Live Reporting
Every morning at 07:00 JST we process real ETC cards and publish the delivery accuracy and reliability — sanitized, aggregate proof only.
Reports delivered today
Every real report we emailed today across the whole platform — the scheduled 07:00 runs PLUS manual and onboarding sends. Read from the production run log; tracked separately from the strict 14-day burn-in scorecard below.
Last 14 days — all real deliveries
| Date (JST) | Delivered | Delivered (07:00) | Delivered (manual) | Failed |
|---|---|---|---|---|
| 2026-09-08 | 10 | 10 | 0 | 0 |
| 2026-09-07 | 10 | 10 | 0 | 0 |
| 2026-09-06 | 10 | 10 | 0 | 0 |
| 2026-09-05 | 10 | 10 | 0 | 0 |
| 2026-09-04 | 10 | 10 | 0 | 0 |
| 2026-09-03 | 10 | 10 | 0 | 0 |
| 2026-09-02 | 10 | 10 | 0 | 0 |
| 2026-09-01 | 30 | 30 | 0 | 0 |
| 2026-08-31 | 10 | 10 | 0 | 0 |
| 2026-08-30 | 10 | 10 | 0 | 0 |
| 2026-08-29 | 10 | 10 | 0 | 0 |
| 2026-08-28 | 10 | 10 | 0 | 0 |
| 2026-08-27 | 10 | 10 | 0 | 0 |
| 2026-08-26 | 10 | 10 | 0 | 0 |
14-day reliability trackerLast 14 days · auto-updating
Tap any day for detailsLive tracker — all-time
Tracking since 2026-06-12Latest run· Ran 2026-09-08
Daily ETC usage report for 2026-09-07 · 100 ETC cards
Autonomous self-repair at scale
Your reports are not just monitored — they repair themselves. When something goes wrong, the system detects it, retries safely, and learns from the error, all on its own — so your reports keep flowing without interruption.
At least two workers stay reserved solely to clear cards that errored out while the main run is busy (M10 + 2 → M12, M14…) — then, once the run is done, every queued error is processed at once with no fixed limit until the queue is clear.
Heavy report jobs run in the background and respond instantly, so a long batch can never time the system out or trigger a false "service down" alert.
Each report has a time limit. A slow or stuck card simply steps aside for an automatic retry while every other report keeps flowing.
An AI assistant reviews hard failures, applies the safest fix, and remembers what worked — so the same issue is resolved automatically next time.
Reports Delivered — Daily Activity
Every report we delivered each day — all live runs (scheduled + manual) combined. Each card we process gets its report delivered. Tap a day for the breakdown.
Analytics
Showing completed run days only.
Reports delivered — cumulative (growth)
Reconciliation %
Run duration (s)
How we measure scale readiness
As we prepare for wider release, we are not only checking whether reports complete. We are also measuring how long each scheduled batch takes, how many processing workers are used, and how the system performs as volume increases. These measurements help us understand how to scale safely before more customers are added.
What counts as a clean day
A daily test is marked successful only when every expected card is accounted for. That means the report completed, recovered automatically, was intentionally skipped for a clear reason, or was classified for review. Silent failures do not count as success.
Road to full launch
Privacy & safety
The tracker uses summarized test results only. We do not display customer names, card numbers, vehicle details, account credentials, or private report data.