GroundStopNow
Home/Data sources

Airport disruption data sources and update rates

US status comes from the FAA NAS Status feed, polled every 60 seconds. The FAA does not publish UK, Canadian or Australian status; those countries use NATS, NAV CANADA and Airservices Australia, which publish different data at different speeds.

Authority-by-authority comparison

Public disruption data by country, as of November 2026.
CountryAuthorityPublic dataWhat it includesOpen feed
United StatesFAANAS Status JSON and XML; ATCSCC advisoriesGround stops, ground delay programs, closures, delay averages and maximumsYes
United KingdomNATS and airport operatorsAirport status pages, NATS statements, AIS dataFlow regulations and CTOTs in operational systems; airport-level disruption on airport sitesNo public status feed
CanadaNAV CANADA and airport authoritiesNOTAMs, AIP supplements, airport status pagesFacility notices and airport operations; flow control is managed internallyNo public status feed
AustraliaAirservices Australia and airport operatorsNetwork performance dashboard, airport status pagesDaily ground delay program reporting and network performance; live disruption on airport sitesPartial / daily

United States: what we ingest and how often

Primary feed
FAA NAS Status
Poll interval
60 s
Page cache
60 s
Stale warning
10 min
  • Airport events: ground stops, ground delay programs, closures, reason text, average and maximum delay, start and end times.
  • Secondary feed: the FAA airport status XML is used as a fallback if the JSON endpoint is unavailable.
  • Weather: NOAA METAR data is displayed on airport pages, cached for 10 minutes at the edge.
  • Reference data: OurAirports public-domain airport names, codes, coordinates and type.

Official sources: FAA NAS Status · ATCSCC advisories · NOAA aviation weather.

What this site does not publish

  • Live status outside the US. The FAA feed does not contain LHR, YYZ or SYD, and no equivalent public feed exists from NATS, NAV CANADA or Airservices.
  • Flight-level status. We do not know your flight number, aircraft, gate or booking.
  • Backfilled history. The archive starts on November 14, 2026. Months before that are empty because we were not collecting, not because no events occurred.

For UK, Canadian and Australian sources in context, see the disruption status page. For the archive limit, see the 12-month history guide.

How to verify a status before you act on it

  1. Match the timestamp. Every page shows the snapshot time. A status without a visible time is not verifiable.
  2. Open the FAA advisory linked from the airport page when one is published for that airport.
  3. Compare with the airline app. The airline decides whether your specific flight is held, rerouted or cancelled.
  4. Treat a cached snapshot as a warning. If the feed is stale, the page says so; do not rely on it for a go/no-go decision.

Data questions

Is GroundStopNow data official?

The US status is taken directly from the FAA's public NAS Status feed and is not edited. GroundStopNow is an independent publisher and is not affiliated with or endorsed by the FAA.

How often is the data updated?

The collector polls the FAA feed once a minute. Pages are cached for up to 60 seconds and show the snapshot time and data age. If the feed is more than 10 minutes old, the page displays a stale warning.

Does GroundStopNow cover the UK, Canada or Australia?

No live status. The FAA feed covers US airports only. For the UK, Canada and Australia we link to NATS, NAV CANADA and Airservices Australia because none of them publishes a public machine-readable status feed equivalent to the FAA's.

Why does the time on the page differ from the FAA advisory?

Event times are the moments our collector first observed a change, so they can differ from the FAA advisory by up to 60 seconds. Durations inherit that margin.

Can I use the data in a product?

Yes, under the API terms. The status endpoint is free during beta, with a fair-use rate limit and a request to cache for at least 30 seconds.