User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
tokentransit.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 910 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 603 ms | 0 |
| Mon 16 | 0 | 0.0 | 319 ms | 0 |
| Mon 18 | 0 | 0.0 | 175 ms | 0 |
| Mon 21 | 0 | 0.0 | 336 ms | 0 |
| Mon 23 | 0 | 0.0 | 497 ms | 0 |
| Tue 01 | 0 | 0.0 | 420 ms | 0 |
| Tue 03 | 0 | 0.0 | 862 ms | 0 |
| Tue 05 | 0 | 0.0 | 617 ms | 0 |
| Tue 07 | 0 | 0.0 | 319 ms | 0 |
| Tue 09 | 0 | 0.0 | 431 ms | 0 |
| Tue 11 | 0 | 0.0 | 437 ms | 0 |
| Tue 14 | 0 | 0.0 | 592 ms | 0 |
| Tue 16 | 0 | 0.0 | 441 ms | 0 |
| Tue 18 | 0 | 0.0 | 487 ms | 0 |
| Tue 20 | 0 | 0.0 | 591 ms | 0 |
| Tue 23 | 0 | 0.0 | 449 ms | 0 |
| Wed 01 | 0 | 0.0 | 559 ms | 0 |
| Wed 03 | 0 | 0.0 | 54 ms | 0 |
| Wed 05 | 0 | 0.0 | 458 ms | 0 |
| Wed 08 | 0 | 0.0 | 348 ms | 0 |
| Wed 10 | 0 | 0.0 | 472 ms | 0 |
| Wed 12 | 0 | 0.0 | 476 ms | 0 |
| Wed 14 | 0 | 0.0 | 236 ms | 0 |
| Wed 16 | 0 | 0.0 | 339 ms | 0 |
| Wed 19 | 0 | 0.0 | 246 ms | 0 |
| Wed 21 | 0 | 0.0 | 583 ms | 0 |
| Wed 23 | 0 | 0.0 | 662 ms | 0 |
| Thu 01 | 0 | 0.0 | 511 ms | 0 |
| Thu 03 | 0 | 0.0 | 359 ms | 0 |
| Thu 05 | 0 | 0.0 | 191 ms | 0 |
| Thu 07 | 0 | 0.0 | 219 ms | 0 |
| Thu 09 | 0 | 0.0 | 524 ms | 0 |
| Thu 11 | 0 | 0.0 | 631 ms | 0 |
| Thu 13 | 0 | 0.0 | 290 ms | 0 |
| Thu 16 | 0 | 0.0 | 241 ms | 0 |
| Thu 18 | 0 | 0.0 | 285 ms | 0 |
| Thu 20 | 0 | 0.0 | 755 ms | 0 |
| Thu 22 | 0 | 0.0 | 665 ms | 0 |
| Fri 00 | 0 | 0.0 | 947 ms | 0 |
| Fri 02 | 0 | 0.0 | 641 ms | 0 |
| Fri 04 | 0 | 0.0 | 162 ms | 0 |
| Fri 06 | 0 | 0.0 | 510 ms | 0 |
| Fri 08 | 0 | 0.0 | 303 ms | 0 |
| Fri 10 | 0 | 0.0 | 435 ms | 0 |
| Fri 12 | 0 | 0.0 | 307 ms | 0 |
| Fri 14 | 0 | 0.0 | 648 ms | 0 |
| Fri 17 | 0 | 0.0 | 490 ms | 0 |
| Fri 18 | 0 | 0.0 | 910 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Token Transit yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Token Transit goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Token Transit alerts to Slack, Discord or a webhook — free.
Token Transit, at tokentransit.com, is one of the Cloud & developer services we monitor. Make public transit the first choice by making it the easiest choice. Token Transit simplifies fare distribution, collection, and management for both transit agencies and riders alike.
Token Transit publishes an official status page at status.tokentransit.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 541 ms average, 59–947 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Token Transit incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
541 ms on average over the last 24 hours (59–947 ms).
Yes, at https://status.tokentransit.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Token Transit here at once, the problem is on Token Transit's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Token Transit. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.