Realtime reliability.
Of 166 agencies we monitor for realtime, the median feed responded 100.0% of the time, with the data arriving about 10 seconds behind real time.
Where feeds stand
| Reliability | Feeds |
|---|---|
| Reliable (99%+ uptime) | 123 |
| Mostly up (90–99%) | 2 |
| Spotty (under 90%) | 41 |
Most reliable
Feeds that responded on nearly every check, freshest first. A target to aim for.
| Agency | State | Uptime | Median lag (s) | Score trend |
|---|---|---|---|---|
| Bay Area Rapid Transit (BART) | California | 100.0% | 0 | |
| Beach Cities Transit | California | 100.0% | 0 | |
| Commerce Municipal Bus Lines | Unlocated | 100.0% | 0 | |
| Emery Go-Round | California | 100.0% | 0 | |
| Intercity Transit | Washington | 100.0% | 0 | |
| Merced County Transit (The Bus) | California | 100.0% | 0 | |
| Merced County Transit (The Bus) | Unlocated | 100.0% | 0 | |
| Mountain Line Transit | Arizona | 100.0% | 0 | |
| Mountain View Transportation Management Association (MVgo) | California | 100.0% | 0 | |
| Orange County Transportation Authority (OCTA) | California | 100.0% | 0 |
By state
| State | Feeds | Median uptime | Reliable |
|---|---|---|---|
| Unlocated | 70 | 100.0% | 55 |
| California | 20 | 100.0% | 15 |
| New York | 12 | 100.0% | 11 |
| Washington | 7 | 100.0% | 6 |
| Oregon | 6 | 100.0% | 5 |
| Ohio | 4 | 77.2% | 1 |
| Florida | 3 | 1.0% | 1 |
| Kentucky | 3 | 0.0% | 1 |
| Maryland | 3 | 100.0% | 3 |
| Minnesota | 3 | 100.0% | 2 |
| Pennsylvania | 3 | 100.0% | 3 |
| Texas | 3 | 89.5% | 1 |
| Arizona | 2 | 100.0% | 2 |
| Colorado | 2 | 100.0% | 2 |
| Georgia | 2 | 50.0% | 1 |
| Maine | 2 | 50.0% | 1 |
| Massachusetts | 2 | 50.0% | 1 |
| North Carolina | 2 | 0.0% | 0 |
| South Carolina | 2 | 100.0% | 2 |
| Virginia | 2 | 50.0% | 1 |
| Wisconsin | 2 | 100.0% | 2 |
| Alaska | 1 | 0.0% | 0 |
| Connecticut | 1 | 68.6% | 0 |
| Idaho | 1 | 100.0% | 1 |
| Illinois | 1 | 100.0% | 1 |
| Indiana | 1 | 100.0% | 1 |
| Iowa | 1 | 100.0% | 1 |
| Louisiana | 1 | 0.0% | 0 |
| Michigan | 1 | 100.0% | 1 |
| Missouri | 1 | 100.0% | 1 |
| Rhode Island | 1 | 98.1% | 0 |
| Tennessee | 1 | 100.0% | 1 |
In plain words: a realtime feed is only useful if it is actually up and current. This tracks whether each agency's feed responded when we checked and how far behind real time it was. An agency that publishes no realtime feed is not counted here and is never penalized for it.
Reliability is the share of monitor runs the feed responded to, over the recorded window; freshness is the median header lag. It never changes a grade. The same data is at the realtime API (realtime.json). Sampling is periodic, not continuous, so this is a reliability signal, not a complete uptime log.