Live aviation GPS jamming and spoofing across 426 Flight Information Regions worldwide. Built on top of gpsjam.org's H3-hex aircraft-NIC dataset (CC-BY, John Wiseman / ADS-B Exchange), re-aggregated per FIR with an aircraft-weighted ratio and a per-FIR confidence tier. 327 FIRs currently meet the confidence threshold; the rest render gray. For sub-day resolution and per-FIR alerts, see programmatic access.
Hot zones: Baltic GPS jamming · Middle East GPS interference · South Asia GPS spoofing · Africa & Mediterranean
Legend ▾
Top FIRs by 7-Day Average
Ranked by 7-day mean jamming ratio. Trend arrow compares this week vs the previous 7-day window. Click a row to fly the map there.
| FIR | Country / Region | 7d avg | 24h | Trend | Level |
|---|---|---|---|---|---|
| UUWV | 17.7% | 19.5% | ↑ | ELEVATED | |
| ULLL | 13.4% | 10.3% | — | ELEVATED | |
| VYYF | 13.0% | 11.8% | — | ELEVATED | |
| URRV | 10.4% | 6.6% | — | ELEVATED | |
| OIIX | Iran | 8.4% | 8.5% | — | MODERATE |
| EFIN | 8.3% | 11.1% | — | MODERATE | |
| UWWW | 6.8% | 3.5% | ↓ | MODERATE | |
| LTAA | Turkey | 6.5% | 7.6% | — | MODERATE |
| USSV | 5.9% | 6.0% | ↓ | MODERATE | |
| OOMM | Oman | 5.6% | 0.0% | ↓ | MODERATE |
| UATT | 5.4% | 4.9% | — | MODERATE | |
| LTXX | 5.4% | 5.9% | — | MODERATE |
GPS Interference by Region
Persistent GPS jamming and spoofing patterns are concentrated in five well-documented regions. Click any region to jump the map there.
Eastern Mediterranean & Persian Gulf GPS spoofing
Cyprus (LCCC), Lebanon (OLBA), Israel (LLLL), Egypt (HECC), and the OEJD/OEDF Saudi sectors have shown persistent GPS spoofing since late 2023. Aircraft regularly report degraded GPS integrity through these airspaces; some operators carry workarounds in their Standard Operating Procedures. Iran (OIIX) and Iraq (ORBB) jamming is conflict-driven and intermittent.
Baltic GPS jamming corridor
Estonia, Latvia, Lithuania, Finland, Poland, and Sweden experience persistent GPS jamming attributed to transmitters in Kaliningrad and adjacent areas, ongoing since 2022. Several airlines have rerouted or suspended Baltic schedules; ILS-reliance has increased on affected approaches. EASA published Conflict Zone Information Bulletins covering parts of this corridor.
India & Pakistan GPS interference
South Asia surfaced as a notable GPS interference zone after Phase C global expansion. Indian FIRs (VAAH Ahmedabad, VOMM Chennai, VOBG/VOBL Bangalore) have shown elevated jamming ratios in early observations. Pakistani airspace (OPKR Karachi, OPLR Lahore) sees intermittent interference correlated with regional tensions.
North Africa & Sahel airspace risk
Libya (HLLL), Sudan (HSSS), Somalia (HCSM), and the Sahel corridor (DAAA Algeria, GMAC Morocco, GVSC Cape Verde) have shown a mix of jamming and spoofing patterns linked to regional conflicts and military operations. Coverage is sparser than MENA due to fewer ADS-B receivers.
Romanian (LRBB), Moldovan (LUKK), Bulgarian (LBSR), and Ukrainian sectors (UKBV, UKLV) adjacent to the conflict zone show intermittent GPS interference spikes correlated with conflict dynamics. Smaller hotspots: Caucasus corridor (UDDD Armenia, UGGG Georgia), Kaliningrad-adjacent Polish airspace, and parts of Central Asia. Coverage of these regions improves as OpenSky receivers come online.
Methodology
The underlying interference signal is the daily H3-resolution-4 dataset published by gpsjam.org (John Wiseman), derived from ADS-B Exchange aircraft NIC reports. A hex is flagged "bad" when ≥10% of aircraft inside it report low navigation integrity over a 24-hour window. Licensed CC-BY; we mirror nothing — we re-aggregate per FIR.
For each H3 hex we compute its centroid, then PostGIS ST_Contains against the
VATSPY FIR polygon set. The per-FIR jamming ratio is aircraft-weighted across
all hexes intersecting that FIR over the last 7 days (Σ bad aircraft / Σ total aircraft) — a single noisy hex with
two aircraft cannot dominate a busy FIR.
Each FIR carries a confidence label based on hex coverage and aircraft volume: High (≥50% hexes with data and ≥200 aircraft over 7d), Medium (≥25%, ≥50 aircraft), Low (sparse), None (no observations). The map colours only High and Medium; Low / None render gray. Top-N and "recent jumps" are High-only.
- • Daily snapshot — gpsjam publishes one CSV per UTC day; this map refreshes at 06:30 UTC.
- • NIC ≠ proof of jamming — low-integrity reports correlate strongly with jamming and spoofing but can also indicate receiver degradation or solar weather.
- • Hex assignment by centroid — a hex straddling two FIRs is attributed wholly to whichever contains its centroid. Material edge cases would require area-weighted assignment (planned).
- • ADS-B receiver coverage — sparse over oceans, central Africa, parts of Asia; affected FIRs surface as Low / None confidence.
Full methodology: /methodology/
Source Lineage
- Upstream signal
- gpsjam.org by John Wiseman — H3-res4 daily aircraft-NIC aggregates
- Raw aircraft data
- ADS-B Exchange — community-pooled ADS-B reception network
- FIR boundaries
- VATSPY Data Project (open data, community-curated)
- FlySafe derivation
- H3 hex centroid → PostGIS
ST_Contains→ aircraft-weighted per-FIR ratio + confidence tier - License
- Upstream CC-BY 4.0 — please credit John Wiseman / ADS-B Exchange when reusing
- Update cadence
- Daily snapshot 06:30 UTC (gpsjam publishes ~04:00 UTC for the prior day)
- Last refresh
- 28 Jun 2026, 07:01 UTC
Citation
Use this citation when referring to the dataset:
FlySafe Global GPS Interference Map, snapshot of 28 Jun 2026, 07:01 UTC. Derived from OpenSky Network ADS-B (CC-BY 4.0). Available at https://flysafe.zone/tools/gps-interference-regional-map/
Programmatic API Access
This snapshot reflects the last 24 hours of GPS interference monitoring. For operational decisions requiring sub-hour resolution, programmatic API access is available to verified operators.
Request API access
15-minute resolution · per-FIR alerts · 400+ FIRs
Frequently Asked Questions
What is GPS jamming and how does it affect aviation? +
GPS jamming is the deliberate or incidental transmission of radio signals on GPS frequencies, blocking or weakening the satellite signal that aircraft rely on for navigation. Most modern airliners can fall back to inertial navigation systems and ground-based navaids, so jamming rarely causes immediate danger — but it forces flight crews to use backup procedures, can affect approaches that depend on GPS (LPV/LNAV/VNAV), and is a strong indicator of nearby military activity or conflict.
How is this map different from GPSJam.org? +
It is built on top of GPSJam.org, not parallel to it. John Wiseman / GPSJam.org publishes a daily H3-hexagon GPS interference dataset under CC-BY, derived from ADS-B Exchange aircraft NIC reports. FlySafe pulls that dataset daily, intersects every hex centroid with FIR polygons via PostGIS, and produces an aircraft-weighted per-FIR roll-up with a confidence tier (so a FIR with only sparse coverage shows as "no data" rather than a misleading 0% or 100%). Where GPSJam shows raw hexes, we show the operational unit pilots and dispatchers work in (FIR). Both surfaces serve complementary use cases; we credit the upstream source on every page.
Is GPS jamming the same as GPS spoofing? +
No. Jamming overwhelms GPS signals so receivers report no fix. Spoofing transmits fake GPS signals, so receivers report a wrong fix — believing they are somewhere they are not. Both show up as NACp degradation on ADS-B, so this map captures both types under one signal. Spoofing is generally more dangerous because it can mislead a flight crew without obvious warning; ICAO and IATA have flagged spoofing as an emerging operational risk, particularly in the Middle East and Eastern Mediterranean since 2023.
Why does my region show as gray (no data)? +
ADS-B Exchange does not have receiver coverage there, or the FIR did not accumulate enough aircraft observations in the last 7 days to clear our confidence threshold. We deliberately show "no data" rather than guess a 0% or invent a colour — sparse FIRs would otherwise look misleadingly safe. Coverage improves as the ADS-B Exchange community adds receivers; the map fills in over time.
How often is the map updated? +
Daily at 06:30 UTC. We pull the latest GPSJam.org H3 dataset (which itself publishes around 04:00 UTC for the prior day) and re-aggregate to FIR level. For sub-day resolution, the upstream gpsjam.org publishes hex-level data, and our paid FIR-level API supports tighter polling for operational use.
Can I use this data in a published article or report? +
Yes — under the CC-BY 4.0 license. Use the citation block above; please include a link back to flysafe.zone/tools/gps-interference-regional-map/. For high-resolution visuals, custom timeframes, or quote-ready statements for press, contact [email protected].
Related Resources
Reference dataset. Daily snapshot. See Terms of Service for data use.