What the map knows.
And what it doesn’t.
Public observations, not every journey
Aircraft and ships transmit position reports that receiver networks collect. Reception changes with geography, equipment, weather and participation. A blank area is not proof that a route has stopped operating.
Live layers
ADSB.lol supplies community aircraft observations within 250 nautical miles of the selected region centre. Public data is available under the Open Database Licence 1.0. Our normalized aircraft extracts remain available under that licence. Please retain attribution and follow its share-alike requirements.
Fintraffic / Digitraffic supplies AIS vessel observations from Finnish and Baltic receiver coverage under CC BY 4.0. We filter and normalize the data. Credit: Fintraffic / digitraffic.fi. This is not worldwide satellite AIS coverage.
Recorded history and sample archives
A server collector requests regional snapshots every 15 minutes. Recordings are retained for 30 days. Provider outages or collector downtime can leave gaps.
The flight replay sample contains 400 aircraft per hourly frame on 17–18 September 2026, derived from ADSB.lol heatmap archives. Frame timestamps are archive observation times; individual radio-report age is not available in the heatmap. Some headings are derived from the preceding snapshot. It is a bounded sample, not complete traffic or continuous trajectories.
The ship replay sample is from NOAA Office for Coastal Management / U.S. Coast Guard AIS archives. It covers Greater New York Harbor on 3 January and 8 November 2023, with up to 50 in-region vessels per day and 15-minute sampling. This United States government data is supplied without a completeness or navigation guarantee.
These aircraft and ship sample dates differ. The timeline displays observations only on their actual dates. It does not invent a matching layer for another date.
When a disruption will glow red
Example legend only. No current disruption is asserted.
A red highlight is reserved for a sustained reduction of at least 60% against a sufficiently stable historical norm. The detector requires at least 14 different comparable days, enough normal traffic, three consecutive affected observations and a stable source-observation coverage proxy. A single missing report cannot trigger it.
The current archive does not meet those requirements. Live disruption alerts are therefore unavailable. The detector compares spatial observation density at the same UTC hour, rather than reconstructing complete routes. Stable counts elsewhere are only a coverage proxy; local receiver outages can still cause false positives. Even a future qualified signal will be labelled as possible until independently corroborated.
Map attribution
Map data © OpenStreetMap contributors. Raster tiles are served by OpenStreetMap.
Do not use this website for navigation, emergency response or safety-critical decisions.