HN Debrief

Tracing a powerful GNSS interference source over Europe

  • Infrastructure
  • Security
  • Europe
  • Aviation
  • Defense

The paper analyzes bursts of interference that have degraded GNSS reception across Europe, Greenland, and Canada since 2019 and says it can identify one source with high confidence: Cosmos 2546, part of Russia’s EKS missile-warning constellation. The authors do not claim a single satellite explains every event. Their point is that at least one EKS satellite was in the right place during each measured incident, which makes the constellation the likely collective source. That is the novelty here. Russia’s GPS disruption near Kaliningrad, the Baltic, and the Black Sea was already well known to pilots, mariners, and people working near those borders. What changed is the evidence that some of this interference is coming from space, which means far wider reach and a harder countermeasure problem than ground transmitters.

If your systems assume GNSS is a stable utility, that assumption is now weak. Treat positioning and timing as contested infrastructure and plan backups for aviation, shipping, logistics, telecom timing, and any field operation near serious state actors.

Discussion mood

Concerned and unsurprised. The dominant view was that Russian GNSS interference has been obvious for years, but the paper is still alarming because it ties some of it to satellites, which implies larger coverage, greater sophistication, and bigger consequences for civilian infrastructure that has no real backup.

Key insights

  1. 01

    The paper implicates a constellation, not one satellite

    Cosmos 2546 is the cleanest identified source, but it cannot explain the full timeline because it was launched after the earliest 2019 events and was not over Europe for every later event. The stronger claim is about the EKS constellation as a whole. That matters because it turns the result from a single bad actor in orbit into an enduring capability built into a military system.

    Read this as evidence of a standing space-based interference capability, not a one-off anomaly. Risk planning should assume repeatable coverage as long as the constellation stays up.

      Attribution:
    • jeroenhd #1
    • NKosmatos #1
  2. 02

    Interference may be incidental, not a dedicated jammer

    The most technical pushback was against the label "jamming." One commenter argued the observed bursts look more like a periodic transmission near GPS L1 that knocks down carrier-to-noise by about 10 dB for a few seconds than an all-out denial waveform. That reframes the issue. A dual-use or adjacent mission signal can still break real receivers, which means operators do not get to care much about intent.

    When you harden products, design against adjacent-band and burst interference, not just textbook jammers. Receiver robustness and filtering matter even if the source was not built primarily to blind navigation.

      Attribution:
    • scotty79 #1 #2
    • DumpoLumbo #1
  3. 03

    The power budget is plausible

    Several comments filled in the missing physical intuition. GNSS arrives at Earth incredibly weak, and receivers pull it out of noise by correlation with known spreading codes. That means you do not need absurd transmitter power to cause trouble. A multi-kilowatt satellite is normal, and Molniya orbits let these spacecraft spend time in geometries that can illuminate large high-latitude regions effectively.

    Do not dismiss space-based interference on gut feel about distance and power. If a weak-signal system is mission critical, validate its resilience empirically instead of assuming orbital sources are too faint to matter.

      Attribution:
    • awestroke #1
    • masklinn #1
    • ralferoo #1
  4. 04

    Backup PNT has been neglected

    The strongest infrastructure point was that cheap jammers have disrupted airports before, yet backup positioning, navigation, and timing systems still lag. eLoran, VOR, DME, aviation MON planning, inertial navigation, and Iridium PNT were all mentioned as partial answers. None is universal. The pattern is clear though. Countries that invested in layered PNT look better prepared than those that treated GNSS as a permanent free utility.

    Map where your business depends on satellite-derived position or time, then assign a fallback for each dependency. The right answer will be a stack, not a single replacement technology.

      Attribution:
    • throw0101a #1
    • mrngld #1
    • throw0101c #1
    • bananaowl #1
    • ifwinterco #1
  5. 05

    The maps understate interference in Ukraine

    A useful correction was that popular GNSS-jam maps often infer trouble from ADS-B reports from civilian aircraft. Ukraine's closed airspace leaves a giant observation hole, so the lack of visible disruption there is a data gap, not evidence of cleaner spectrum. Commenters added that Ukraine also jams heavily itself to defend against drones and guided munitions, which makes the local environment even less representative of public maps.

    Be careful using public interference maps as ground truth. If the measurement source is opportunistic, the blank spots may be where the problem is worst.

      Attribution:
    • forgotTheLast #1
    • sorenjan #1
    • lefty2 #1

Against the grain

  1. 01

    For pilots this is old news

    Aviation people pushed back on the idea that the operational impact is newly shocking. Near Russia's western border, pilots have expected GNSS trouble for years and fall back to inertial systems and procedure. From that angle, the paper is more about attribution and mechanism than a sudden change in day-to-day flight safety.

    Separate attribution value from operational novelty. If you work in an affected sector, ask whether the discovery changes your procedures or mainly strengthens the political and technical case for investment.

      Attribution:
    • avazhi #1
  2. 02

    Some high-profile jamming anecdotes were overstated

    One commenter argued that a widely repeated claim about Ursula von der Leyen's aircraft being disrupted near Plovdiv was contradicted by public flight tracking data. The point is not to exonerate interference. It is that public discussion around GNSS disruption easily accumulates dramatic stories that do not survive basic telemetry checks.

    Treat viral EW anecdotes the way you treat outage rumors. Verify against raw tracking and sensor data before using them to justify strategy or policy.

      Attribution:
    • sam_lowry_ #1 #2

In plain english

ADS-B ↩
Automatic Dependent Surveillance-Broadcast, a system where aircraft broadcast their identity and position so they can be tracked.
carrier-to-noise ↩
A measure of how strong a received radio signal is compared with background noise, which affects whether a receiver can lock onto it.
DME ↩
Distance Measuring Equipment, a radio system aircraft use to measure distance from ground stations.
EKS ↩
Edinaya Kosmicheskaya Sistema, Russia’s space-based early warning satellite constellation for missile launch detection.
eLoran ↩
Enhanced Long Range Navigation, a terrestrial radio navigation and timing system often proposed as a backup to satellite navigation.
GNSS ↩
Global Navigation Satellite System, the general term for satellite-based positioning systems such as GPS, GLONASS, Galileo, and BeiDou.
GPS ↩
Global Positioning System, the United States satellite navigation system used for location and precise timing.
Iridium PNT ↩
A positioning, navigation, and timing service built on the Iridium satellite network as an alternative or complement to GNSS.
L1 ↩
A primary radio frequency band used by many GNSS signals, including the main civilian GPS signal.
MON ↩
Minimum Operating Network, the Federal Aviation Administration plan to preserve a minimal backup network of conventional radio navigation aids.
PNT ↩
Positioning, Navigation, and Timing, the combined services many systems derive from GNSS.
thermal noise floor ↩
The natural background electrical noise present in receivers, below which a radio signal cannot be directly seen without special processing.
VOR ↩
VHF Omnidirectional Range, a ground-based aviation radio navigation system.

Reference links

Live maps and monitoring

Background explainers

Backup navigation and timing

Aviation and policy context

Space debris and orbit risk

Incidents and regional context