NTD readiness.
58.1% of 1024 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 | 595 |
| At risk | 117 |
| Not ready | 312 |
Reporters, not feeds
Of the 1,253 NTD reporters that operated at least one fixed-route mode in Report Year 2024, between 35 and 48 have no GTFS link reported to FTA and no feed found in the three open catalogs this site reads (this project's registry, the Transitland Atlas, and the Mobility Database). The others either report a GTFS link to FTA or are matched to a feed in those catalogs. The low end counts a shared rare word in an agency name as a catalog 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 |
| GTFS link reported to FTA, not matched to a catalog | 593 |
| Name overlap only, needs a human | 13 |
| No GTFS link reported and no candidate in the catalogs read | 35 |
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 link and no catalog match is a limit of what these sources 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. A GTFS link in FTA's NTD data is self-reported by the agency and is not fetched or validated by this project. It shows that the agency has told FTA
where its feed is, not that the feed is current or valid. The link table has no
report-year column, so it is matched by NTD ID against the Report Year
2024 reporters; it was retrieved
2026-10-23. 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. In 2022 FTA proposed that a reporter without a GTFS feed could request a one-year waiver by documenting that it is seeking technical assistance; we have not confirmed how that waiver works under the current rule, so ask your NTD validation analyst. 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 1056 days ago, so FTA would find the link out of date. | |
| Academy Bus | New York | Service data expired 1319 days ago, so FTA would find the link out of date. | |
| Alcatraz Cruises Ferry | California | Service data expired 20 days ago, so FTA would find the link out of date. | |
| Amarillo City Transit | Texas | Service data expired 1786 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. | — |
| Antelope Valley Transit Authority (AVTA) | California | Service data expired 1938 days ago, so FTA would find the link out of date. | |
| Areawide Community Transportation System | Alabama | Service data expired 417 days ago, so FTA would find the link out of date. | |
| Astoria Riverfront Trolley | Oregon | Service data expired 20 days ago, so FTA would find the link out of date. | |
| Atlanta Streetcar | Georgia | Service data expired 3247 days ago, so FTA would find the link out of date. | |
| Avalon Transit | California | Service data expired 965 days ago, so FTA would find the link out of date. | |
| Bandelier National Monument Shuttle | New Mexico | Service data expired 38 days ago, so FTA would find the link out of date. | |
| Bellflower Bus | California | Service data expired 82 days ago, so FTA would find the link out of date. | |
| Benson Area Transit | Arizona | Service data expired 325 days ago, so FTA would find the link out of date. | |
| Bethesda Circulator | Maryland | No service end date could be read, so currency is unknown. | — |
| Birmingham Jefferson County Transit Authority (MAX) | Alabama | No service end date could be read, so currency is unknown. | — |
| Boston Harbor Islands Ferry | Massachusetts | Service data expired 40 days ago, so FTA would find the link out of date. | |
| Breckenridge Free Ride | Colorado | Service data expired 223 days ago, so FTA would find the link out of date. | |
| Brite | Virginia | Service data expired 324 days ago, so FTA would find the link out of date. | |
| Bryce Canyon Shuttle | Utah | Service data expired 34 days ago, so FTA would find the link out of date. | |
| Butte Regional Transit (B-Line) | Montana | Service data expired 329 days ago, so FTA would find the link out of date. | |
| Cape Cod Regional Transportation Authority (Cape Cod RTA) | Massachusetts | Service data expired 40 days ago, so FTA would find the link out of date. | |
| Caravan Airport Transportation | Oregon | Service data expired 20 days ago, so FTA would find the link out of date. | |
| Carlsbad Municipal Transit System | New Mexico | Service data expired 325 days ago, so FTA would find the link out of date. | |
| Cat Tran Shuttle | Arizona | Service data expired 708 days ago, so FTA would find the link out of date. | |
| Charm City Circulator | Maryland | Service data expired 1727 days ago, so FTA would find the link out of date. | |
| Chatham Area Transit (CAT) | Georgia | Service data expired 482 days ago, so FTA would find the link out of date. | |
| Cherokee Area Transportation System (CATS) | Georgia | Service data expired 4708 days ago, so FTA would find the link out of date. | |
| Citibus | Iowa | Service data expired 690 days ago, so FTA would find the link out of date. | |
| Citrus County Transit | Florida | No service end date could be read, so currency is unknown. | — |
| City Coach | California | Service data expired 144 days ago, so FTA would find the link out of date. | |
| City of Bell (La Campana) | California | Service data expired 21 days ago, so FTA would find the link out of date. | |
| City of Glendale | California | No service end date could be read, so currency is unknown. | — |
| City of Hinesville, Georgia | Georgia | Service data expired 750 days ago, so FTA would find the link out of date. | |
| City of Las Vegas | Nevada | Service data expired 509 days ago, so FTA would find the link out of date. | |
| City of Winona MN - Winona Transit Service | Minnesota | Service data expired 324 days ago, so FTA would find the link out of date. | |
| Clackamas Community College (CCC) Xpress | Oregon | Service data expired 1543 days ago, so FTA would find the link out of date. | |
| Cortland County Public Transportation | New York | No service end date could be read, so currency is unknown. | — |
| Cotton Express and Central Arizona Regional Transit | Arizona | Service data expired 690 days ago, so FTA would find the link out of date. | |
| Cudahy Area Rapid Transit | California | No service end date could be read, so currency is unknown. | — |
| Cuyahoga Valley Scenic Railroad | Ohio | No service end date could be read, so currency is unknown. | — |
Showing 40 of 290 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 | 9 | 2 | 9 | 20 |
| Arkansas | 0 | 0 | 2 | 2 |
| California | 101 | 20 | 79 | 200 |
| Colorado | 66 | 6 | 14 | 86 |
| Connecticut | 8 | 0 | 1 | 9 |
| Delaware | 0 | 1 | 0 | 1 |
| District of Columbia | 0 | 0 | 4 | 4 |
| Florida | 15 | 5 | 20 | 40 |
| Georgia | 3 | 1 | 10 | 14 |
| Hawaii | 1 | 1 | 1 | 3 |
| Idaho | 2 | 0 | 1 | 3 |
| Illinois | 6 | 5 | 2 | 13 |
| Indiana | 7 | 1 | 2 | 10 |
| Iowa | 18 | 0 | 1 | 19 |
| Kansas | 2 | 2 | 1 | 5 |
| Kentucky | 3 | 1 | 0 | 4 |
| Louisiana | 4 | 0 | 0 | 4 |
| Maine | 1 | 2 | 3 | 6 |
| Maryland | 11 | 3 | 13 | 27 |
| Massachusetts | 19 | 3 | 15 | 37 |
| Michigan | 8 | 1 | 4 | 13 |
| Minnesota | 6 | 2 | 2 | 10 |
| Mississippi | 1 | 1 | 1 | 3 |
| Missouri | 2 | 1 | 3 | 6 |
| Montana | 3 | 0 | 5 | 8 |
| Nebraska | 1 | 1 | 1 | 3 |
| Nevada | 3 | 1 | 2 | 6 |
| New Hampshire | 2 | 0 | 1 | 3 |
| New Jersey | 2 | 2 | 1 | 5 |
| New Mexico | 5 | 2 | 7 | 14 |
| New York | 39 | 11 | 28 | 78 |
| North Carolina | 9 | 2 | 5 | 16 |
| North Dakota | 2 | 0 | 1 | 3 |
| Ohio | 8 | 3 | 4 | 15 |
| Oklahoma | 2 | 0 | 1 | 3 |
| Oregon | 43 | 6 | 21 | 70 |
| Pennsylvania | 23 | 3 | 3 | 29 |
| Rhode Island | 2 | 0 | 1 | 3 |
| South Carolina | 4 | 1 | 1 | 6 |
| South Dakota | 0 | 0 | 1 | 1 |
| Tennessee | 5 | 1 | 3 | 9 |
| Texas | 16 | 2 | 3 | 21 |
| Unlocated | 15 | 1 | 3 | 19 |
| Utah | 4 | 1 | 2 | 7 |
| Vermont | 10 | 2 | 3 | 15 |
| Virginia | 39 | 10 | 4 | 53 |
| Washington | 50 | 7 | 14 | 71 |
| West Virginia | 1 | 0 | 1 | 2 |
| Wisconsin | 8 | 2 | 1 | 11 |
| Wyoming | 0 | 0 | 1 | 1 |
A state name that is a link opens that state's Report Year 2026 list of tracked feeds, with the shapes.txt and agency_id checks for each.
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.