NTD readiness.
52.7% of 1006 tracked feeds look ready to certify against four feed checks for RY2026: the feed is published at a working URL, it is valid, its calendar has not lapsed, and agency.txt provides agency_id for the P-50 crosswalk.
Where feeds stand
| Status | Feeds |
|---|---|
| Ready to certify | 530 |
| At risk | 137 |
| Not ready | 339 |
Reporters, not feeds
Of the 1,253 NTD reporters that operated at least one fixed-route mode in Report Year 2024, between 473 and 641 have no feed discoverable in any open catalog this site reads. The low end counts a shared rare word in an agency name as a match; the high end does not. The gap between them is how wide a name-based join is, and it is stated rather than averaged away.
| Reporters | Count |
|---|---|
| Matched to a feed this site tracks | 573 |
| Feed found in another open catalog | 39 |
| Name overlap only, needs a human | 168 |
| No candidate found anywhere | 473 |
These are counts of NTD reporters. The
1,253 above is a different denominator from the tracked-feed
count at the top of this page, which counts feed records: one operator can
publish several, and a regional feed can carry many operators. The two are never
added. A reporter with no discoverable feed is a limit of what open catalogs
can see, not a finding about that agency, and the fix may belong to FTA's own
crosswalk or to a catalog rather than to the agency. Report year
2024, retrieved 2026-08-15;
sources and terms are in data/ntd/PROVENANCE.md.
Report year 2026: small and rural reporters join
Since Report Year 2023, NTD reporters with fixed-route service have had to publish and maintain GTFS. For RY2026, every submission must provide a stable agency_id for each represented reporter and crosswalk it to the reporter's NTD ID on P-50; agency_id does not need to equal that five-digit ID. An agency that cannot comply yet can request a one-year waiver by showing it is pursuing technical assistance to establish its GTFS data. The same rule adds shapes.txt to the published feed: does your feed need shapes.txt, explained.
One fix from ready
Each of these feeds is a single fix away from looking ready to certify. The fix column is written to be forwarded as-is.
| Agency | State | The one fix | Trend |
|---|---|---|---|
| 81 Connection, CityGo, KanConnect | Kansas | Service data expired 1012 days ago, so FTA would find the link out of date. | |
| Academy Bus | New York | Service data expired 1275 days ago, so FTA would find the link out of date. | |
| Amarillo City Transit | Texas | Service data expired 1742 days ago, so FTA would find the link out of date. | |
| Anaheim Resort Transportation (ART) | California | No service end date could be read, so currency is unknown. | |
| Annapolis Transit | Maryland | Service data expired 8 days ago, so FTA would find the link out of date. | |
| Antelope Valley Transit Authority (AVTA) | California | Service data expired 1894 days ago, so FTA would find the link out of date. | |
| Areawide Community Transportation System | Alabama | Service data expired 373 days ago, so FTA would find the link out of date. | |
| Atlanta Streetcar | Georgia | Service data expired 3203 days ago, so FTA would find the link out of date. | |
| Avalon Transit | California | Service data expired 921 days ago, so FTA would find the link out of date. | |
| Bay Town Trolley | Florida | Service data expired 312 days ago, so FTA would find the link out of date. | |
| Beach Cities Transit | California | Service data expired 1376 days ago, so FTA would find the link out of date. | |
| Bellflower Bus | California | Service data expired 38 days ago, so FTA would find the link out of date. | |
| Benson Area Transit | Arizona | Service data expired 281 days ago, so FTA would find the link out of date. | |
| Bethesda Circulator | Maryland | Service data expired 737 days ago, so FTA would find the link out of date. | |
| Birmingham Jefferson County Transit Authority (MAX) | Alabama | Service data expired 495 days ago, so FTA would find the link out of date. | |
| Blacksburg Transit | Virginia | Service data expired 69 days ago, so FTA would find the link out of date. | |
| Blue Sky Limo LLC | Colorado | Service data expired 281 days ago, so FTA would find the link out of date. | |
| Breckenridge Free Ride | Colorado | Service data expired 179 days ago, so FTA would find the link out of date. | |
| Breeze Transit | Florida | Service data expired 531 days ago, so FTA would find the link out of date. | |
| Brite | Virginia | Service data expired 280 days ago, so FTA would find the link out of date. | |
| Broward County Transit | Florida | Service data expired 12 days ago, so FTA would find the link out of date. | |
| Butte Regional Transit (B-Line) | Montana | Service data expired 285 days ago, so FTA would find the link out of date. | |
| Capital District Transportation Authority (CDTA) | New York | Service data expired 40 days ago, so FTA would find the link out of date. | |
| Carlsbad Municipal Transit System | New Mexico | Service data expired 281 days ago, so FTA would find the link out of date. | |
| Cascades East Transit (CET) | Oregon | Service data expired 898 days ago, so FTA would find the link out of date. | |
| Cat Tran Shuttle | Arizona | Service data expired 664 days ago, so FTA would find the link out of date. | |
| Charm City Circulator | Maryland | Service data expired 1683 days ago, so FTA would find the link out of date. | |
| Chatham Area Transit (CAT) | Georgia | Service data expired 438 days ago, so FTA would find the link out of date. | |
| Cherokee Area Transportation System (CATS) | Georgia | Service data expired 4664 days ago, so FTA would find the link out of date. | |
| Citibus | Iowa | Service data expired 646 days ago, so FTA would find the link out of date. | |
| Citrus County Transit | Florida | Service data expired 646 days ago, so FTA would find the link out of date. | |
| City Coach | California | Service data expired 100 days ago, so FTA would find the link out of date. | |
| City of Bell (La Campana) | California | Service data expired 646 days ago, so FTA would find the link out of date. | |
| City of Douglas | Arizona | Service data expired 161 days ago, so FTA would find the link out of date. | |
| City of Glendale | California | Service data expired 1499 days ago, so FTA would find the link out of date. | |
| City of Hinesville, Georgia | Georgia | Service data expired 706 days ago, so FTA would find the link out of date. | |
| City of Las Vegas | Nevada | Service data expired 465 days ago, so FTA would find the link out of date. | |
| City of Longview | Texas | Service data expired 8 days ago, so FTA would find the link out of date. | |
| City of Mechanicville Public Transit | New York | Service data expired 13 days ago, so FTA would find the link out of date. | |
| City of Show Low | Arizona | Service data expired 161 days ago, so FTA would find the link out of date. |
Showing 40 of 321 feeds; the full list is in ntd.json.
Source: FTA's NTD reporting changes for report years 2025 and 2026. State programs can reach small agencies through the program rollups, and any expired feed's page carries a ready-to-send outreach note.
By state
| State | Ready | At risk | Not ready | Total |
|---|---|---|---|---|
| Alabama | 3 | 0 | 3 | 6 |
| Alaska | 3 | 1 | 3 | 7 |
| Arizona | 8 | 0 | 12 | 20 |
| Arkansas | 0 | 0 | 2 | 2 |
| California | 92 | 24 | 89 | 205 |
| Colorado | 60 | 10 | 16 | 86 |
| Connecticut | 7 | 0 | 2 | 9 |
| Delaware | 0 | 1 | 0 | 1 |
| District of Columbia | 1 | 1 | 2 | 4 |
| Florida | 12 | 7 | 21 | 40 |
| Georgia | 4 | 0 | 10 | 14 |
| Hawaii | 1 | 1 | 1 | 3 |
| Idaho | 2 | 0 | 1 | 3 |
| Illinois | 8 | 1 | 3 | 12 |
| Indiana | 7 | 0 | 3 | 10 |
| Iowa | 18 | 0 | 1 | 19 |
| Kansas | 2 | 1 | 2 | 5 |
| Kentucky | 3 | 1 | 0 | 4 |
| Louisiana | 3 | 1 | 0 | 4 |
| Maine | 2 | 2 | 2 | 6 |
| Maryland | 8 | 5 | 14 | 27 |
| Massachusetts | 20 | 4 | 13 | 37 |
| Michigan | 8 | 0 | 5 | 13 |
| Minnesota | 7 | 1 | 2 | 10 |
| Mississippi | 1 | 2 | 0 | 3 |
| Missouri | 1 | 2 | 3 | 6 |
| Montana | 3 | 0 | 5 | 8 |
| Nebraska | 2 | 0 | 1 | 3 |
| Nevada | 3 | 1 | 2 | 6 |
| New Hampshire | 1 | 0 | 2 | 3 |
| New Jersey | 2 | 2 | 1 | 5 |
| New Mexico | 5 | 3 | 6 | 14 |
| New York | 35 | 13 | 29 | 77 |
| North Carolina | 9 | 2 | 5 | 16 |
| North Dakota | 2 | 0 | 1 | 3 |
| Ohio | 7 | 3 | 5 | 15 |
| Oklahoma | 2 | 0 | 1 | 3 |
| Oregon | 38 | 12 | 20 | 70 |
| Pennsylvania | 6 | 2 | 5 | 13 |
| Rhode Island | 2 | 1 | 0 | 3 |
| South Carolina | 5 | 0 | 1 | 6 |
| South Dakota | 0 | 0 | 1 | 1 |
| Tennessee | 5 | 0 | 4 | 9 |
| Texas | 12 | 2 | 5 | 19 |
| Unlocated | 11 | 3 | 4 | 18 |
| Utah | 5 | 1 | 1 | 7 |
| Vermont | 9 | 3 | 3 | 15 |
| Virginia | 28 | 14 | 9 | 51 |
| Washington | 49 | 9 | 13 | 71 |
| West Virginia | 0 | 1 | 1 | 2 |
| Wisconsin | 8 | 0 | 3 | 11 |
| Wyoming | 0 | 0 | 1 | 1 |
In plain words: since Report Year 2023, every NTD reporter with fixed-route or deviated-fixed-route service has to publish a valid, current GTFS feed and certify it each year. For RY2026, each represented reporter also needs a stable agency_id crosswalked on P-50. This page reads those four feed signals for every feed we track and rolls them up, so a program can see at a glance how its agencies are doing.
This is a data-quality heads-up, not an official compliance determination. Each agency's annual D-10 certification is the official one. The same numbers are published as JSON at ntd.json.