Call-prep brief · checked 2026-07-09
Connecticut Transit
Grade F · 53.6 / 100
Unchanged since 2026-07-08.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
Top three things to fix
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
Effort: Usually a vendor support ticket.
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
Effort: Usually a vendor support ticket.
Agencies here usually clear this within about 1 week (based on 9 observed fixes).
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
Effort: Usually a vendor support ticket.
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
NTD certification readiness: Ready
This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 196 days.
agency_id and NTD ID: Not aligned. Your feed's agency_id is 4, 5, 3, 2, 1, 7, 8; your National Transit Database ID is 10048. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 10048 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.
Key facts
- Feed URL
- https://www.cttransit.com/sites/default/files/gtfs/googlect_transit.zip
- Last checked
- 2026-07-09
- Service window
- 184 days of service data remain. Last service date 2027-01-09.
- State
- Connecticut
Part of the Connecticut portfolio: see where this agency sits among the state's feeds before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.