Across 50 monitored feed records, the median realtime feed responded 100.0% of the time, with the data arriving about 11 seconds behind real time.
The newest of these 50 feed records was last observed on 2026-11-22; the median on 2026-10-20, and the least recently observed on 2026-10-20. Sampling is periodic, so these are the dates the readings were taken, not the date this page was built.
Where feeds stand
Realtime reliability bandsShare of monitored feeds in each uptime band.
Reliable (99%+ uptime)82%41 of 50 feeds
Mostly up (90–99%)6%3 of 50 feeds
Spotty (under 90%)12%6 of 50 feeds
0%100%
Show the table
Reliability
Feeds
Reliable (99%+ uptime)
41
Mostly up (90–99%)
3
Spotty (under 90%)
6
Most reliable
Comparison-eligible feed records that responded on nearly every check, freshest first. A target to aim for.
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 2493 published feed records; 1661 meet rubric 1.5, scoring profile gtfs-scorecard-1.5, MobilityData gtfs-validator 8.0.1, reader archive profile raw-v1, and measured categories Correctness, Freshness, Rider experience, and 50 have realtime observations used here.