GTFS Scorecard
← All agencies

Arizona agencies

20 feed scorecards · 72.1 out of 100 average · 14 need attention

The average and grade distribution use 12 canonical, non-duplicate feed scorecards under one producer contract: rubric 1.3, scoring profile gtfs-scorecard-1.3, MobilityData gtfs-validator 8.0.1, reader archive profile raw-v1, and measured categories Correctness, Freshness, Rider experience. Every member remains listed below.

Expired feeds 12 of 20

These feeds have run out and dropped from trip planners. Start the program's outreach here.

Recently lapsed 6

Expired within the last year. Likely still running; a re-export with a longer calendar brings each one back into trip planners.

Expired over a year ago 6

Expired more than a year ago. The listed URL is usually still canonical, so the source stopped refreshing. Confirm the agency still runs before reading the grade as a current failure.

Realtime health 2 monitored

All 2 feed records here with a realtime endpoint configured have been sampled by the monitor. Least reliable first. Reachability, how far behind each feed's own timestamp runs, and how much of the scheduled service appears in it. Sampled on a schedule rather than continuously, and it changes no grade.

Across the monitored feeds: median uptime 100.0%, median lag 7s.

shapes.txt coverage 18 of 20

The FTA National Transit Database requires shapes.txt covering every trip (Reduced, Rural, and Tribal reporters by Report Year 2026; Full Reporters already). These agencies are not fully covered yet. Check each one against its own NTD filing.

Fixes shared across this group

The same fix shows up in more than one agency's top 3 here, often the same export setting or scheduling-software step. Worth raising once with every agency it touches.

Feed scorecards: attention first, then alphabetical