Realtime reliability.
Across 1 monitored feed records, the median realtime feed responded 0.0% of the time, with the data arriving about not recorded behind real time.
Every one of these 1 feed records was last observed on 2026-09-04. Sampling is periodic, so these are the dates the readings were taken, not the date this page was built.
Where feeds stand
Show the table
| Reliability | Feeds |
|---|---|
| Reliable (99%+ uptime) | 0 |
| Mostly up (90–99%) | 0 |
| Spotty (under 90%) | 1 |
Most reliable
Comparison-eligible feed records that responded on nearly every check, freshest first. A target to aim for.
| Feed record | Location | Uptime | Median lag (s) | Score trend |
|---|---|---|---|---|
| Tempo Bus (Agglomération d'Agen) | Nouvelle-Aquitaine, France | 0.0% | None |
By country and subdivision
| Location | Feed records | Median uptime | Reliable |
|---|---|---|---|
| France | 1 | 0.0% | 0 |
Show 1 covered subdivision in France
| Subdivision | Feed records | Median uptime | Reliable |
|---|---|---|---|
| Nouvelle-Aquitaine, France | 1 | 0.0% | 0 |
United States by state
| State | Feeds | Median uptime | Reliable |
|---|
In plain words: a realtime feed is only useful if it is actually up and current. This tracks whether each monitored 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. The directory contains 2474 published feed records; 1926 meet rubric 1.4, scoring profile gtfs-scorecard-1.4, MobilityData gtfs-validator 8.0.1, reader archive profile raw-v1, and measured categories Correctness, Freshness, Rider experience, and 1 have realtime observations used here.