TransitFeeds is gone. Here's where transit feed data lives now.
If you're here because transitfeeds.com stopped working, or because a bookmark, script, or documentation link now points at a dead page, here's what happened and where to go instead.
What happened to TransitFeeds?
TransitFeeds launched in 2014 as a community catalog of GTFS feeds and became the default place to browse, download, and archive transit data. It was later renamed OpenMobilityData and maintained by MobilityData, the non-profit that stewards the GTFS spec.
The catalog stopped receiving updated feed data in February 2024, and the site was deprecated in December 2025. Its historical archive (2014–2024) was migrated to MobilityData's replacement platform.
Where to download GTFS feeds now
- Mobility Database: the official successor, run by MobilityData. 6,000+ GTFS, GTFS Realtime, and GBFS feeds in 99+ countries, with an API. This is where TransitFeeds' historical data went, and where trip planners look for new feeds.
- Transitland: an independent feed registry and API maintained by Interline, with feed contents queryable down to the route and stop level.
- The agency itself: most agencies publish their feed at a stable URL on their own site. The Mobility Database record links to the source.
Want to check whether a feed is valid and current?
One thing TransitFeeds did well was show feed status at a glance. Our free GTFS Feed Health dashboard tracks published U.S. feeds continuously: whether they validate against the spec, whether they're expired, and what the canonical validator flags. No account needed.
(It's how we found that roughly 45% of U.S. transit agencies have no GTFS feed any trip planner can find. That's the gap GTFS·X exists to close.)
If you're an agency whose feed was hosted or listed on TransitFeeds
Your feed needs a new permanent home and a listing in the Mobility Database so Google Maps, Apple Maps, and Transit keep finding it:
Host your feed at a stable URL you control (your website, or a hosting service).
Submit it to the Mobility Database (the registry consumers actually poll).
Keep it valid: run it through the canonical GTFS validator whenever it changes.
If you'd rather not manage that by hand, GTFS·X edits and validates feeds free in your browser, and the Planner plan handles hosted publishing and one-click Mobility Database submission. But whichever tools you use: get your feed to a stable URL and into the Mobility Database.