GPS jamming map
Last updated
The map above is the live GPS jamming map: every hexagon where aircraft reported poor satellite position accuracy in the last UTC day, built from open ADS-B data and rebuilt each morning.
What the map shows today
From flights on 7 November 2026: 935 of 24,198 monitored areas worldwide showed high interference and 2,350 medium. This day's page has the region table and a citation.
Each hexagon is about 45 km across. Its colour is the share of aircraft that crossed it and reported a position accuracy of 0.05 nautical miles or worse (ADS-B NACp of 7 or less) at least once that day: green under 3%, yellow 3 to 10%, red above 10%, purple above 50%. A hexagon needs at least three aircraft to be drawn at all, so empty sea and thin airspace stay blank instead of turning green. Every threshold, and the reasoning behind it, is in the methodology.
Why low accuracy points to jamming
A jammer pours noise onto the satellite frequencies. Inside its reach a receiver can't hear the satellites properly, its position error grows, and the aircraft's transponder reports that growing uncertainty in every ADS-B message. If many aircraft in one place report the same loss at the same time, the cause is probably in that place and not in the aircraft. That's what a red cluster means here. It is a sign of jamming or spoofing, not proof, and the map never says who is responsible. The causes page covers what else lowers accuracy, from solar storms to ageing equipment.
Where a government or regulator has put a name to the interference, the region pages say so and link the source. The Baltic Sea, Black Sea, Eastern Mediterranean and Middle East have seen the most sustained interference since the map began, and the regions index lists the rest.
Using the map
Zoom in for named places and click a hexagon for its figures. The day bar at the top steps back through every saved day, and each of those days has its own page under days, with a region table and a citation. Region and country pages add an "Over time" chart and the worst day on record. The data behind all of it is open under the Open Database License through the API, and the map can be embedded on any site, framed on any region.
How it compares with other public maps
| Map | Data | What it draws | Updated | Past days |
|---|---|---|---|---|
| GPSInterference.com | Open ADS-B track history from adsb.lol, every receiver feeding it | Share of aircraft per hexagon reporting NACp of 7 or less: green under 3%, yellow 3–10%, red over 10%, purple over 50% | Once a day, about 04:40 UTC, for the previous UTC day | Every saved day, each with its own page and JSON; open data (ODbL) |
| gpsjam.org | ADS-B from airplanes.live and ADS-B Exchange, by its FAQ | Share of aircraft per hexagon reporting low accuracy: green under 2%, yellow 2–10%, red over 10% | Once a day, soon after midnight UTC | Daily maps back to February 2022 |
| Flightradar24 | ADS-B from Flightradar24's own receivers, by its support page | Areas where a significant number of flights report lowered NIC | Every 6 hours | Not stated |
| GPSwise | ADS-B relayed by the OpenSky Network, by its site | Anomalies in reported positions, flagged as jamming or spoofing | Live, as it describes it | Not stated |
Jamming and spoofing leave nearly the same trace in this data, since both end with a receiver that no longer trusts its position. Jamming versus spoofing explains the difference, the spoofing map page covers what this map can say about spoofing, and how to read a GPS interference map walks through a day on it.