Ionosphere

Watch what is happening in the sky and at sea, with the unusual parts published as signed, open records that anyone can check, cite and build on.

Ionosphere watches open ADS-B aircraft data for emergencies, GPS interference and unusual flight patterns, and open AIS ship data for vessels in distress. It joins reports of the same event, says how well confirmed each one is and why, and publishes every version as a record on AT Protocol. The records belong to the accounts that published them, not to a website, so anyone can run their own copy of this service from the same data.

The map shows the everyday picture — thousands of ships and aircraft going about their business — so an event can be judged against what is normal around it. That live view is exactly that, a view: only events become records.

Open the live map Use the API Read the records

What it detects

EventWhen it is reported
Emergency squawksAn aircraft sets transponder code 7500 (unlawful interference), 7600 (radio failure) or 7700 (general emergency)
Emergency statusAn aircraft broadcasts an ADS-B emergency status without the matching squawk
Rapid descentSustained descent of 5,000 ft/min or more, above 5,000 ft
GPS interferenceIn one area, at least two aircraft, and at least 15% of those there, broadcast degraded satellite navigation (NIC or NACp below the ADS-B minimums)
CirclingTwo or more full circles in 15 minutes, 5,000 ft or more above the ground
HoldingA racetrack pattern for 20 minutes or more, 5,000 ft or more above the ground
Loitering30 minutes within 30 km without orbiting, 5,000 ft or more above the ground
TurnbackA steady course reversed by 120° or more at cruise
Vessel distressAn AIS search-and-rescue transmitter (AIS-SART, man overboard or EPIRB) is active, or a vessel broadcasts a safety message beginning MAYDAY. Test transmissions are ignored

Every aircraft is reported, military and private included. ADS-B is broadcast in the clear by the operator's choice, and the same data is already public. Each event carries the aircraft's open-data flags (military, privacy programmes such as PIA and LADD) so you can filter on them.

How sure is it?

Every event shows a tier, and the facts behind it: which aggregator confirmed it, how many independent stations agreed, and who reviewed it. It never shows a score.

Data relayed from an aggregator is never trusted on its own. It stays Flash until a different aggregator confirms it.

The API

Past events can be searched, filtered and exported. Sign in with any AT Protocol account (a Bluesky account works) at api.ionosphere.network/login to get a free API key. Ionosphere stores your DID and a hash of the key, and no email address or password.

curl -H "Authorization: Bearer ion_…" \
  "https://api.ionosphere.network/v1/events?tier=fixed&flag=military&bbox=38,-78,40,-76"
EndpointReturns
GET /v1/eventsEvents, newest first. Filter by from, to, kind, tier, flag, cell (H3), bbox, icao24, text q; page with limit and cursor
GET /v1/event?uri=Every version of one event, oldest first
GET /v1/export?format=The same selection as GeoJSON, CSV, JSON Lines or Parquet, each row citing its signed record
GET /v1/statsWhat the index holds

The records

Every event is a chain of network.ionosphere.sounding records. Each new version supersedes the last, and none is ever changed, so any version can be cited. Soundings are built from network.ionosphere.ping records, and each sounding names the exact pings it used. You can read them directly from the publishing accounts' repositories, or follow them live through any AT Protocol relay, without using this site at all.

AccountPublishes
did:plc:v7jck74ank374heibwj27dd6Soundings: the fused events
did:plc:oceu7ngnuokgxzcxvsinexhjPings relayed from adsb.fi, each marked as relayed
did:plc:n24fgkf2mpydooqp3rzped26Vessel pings relayed from aisstream.io, each marked as relayed
curl "https://pds.ionosphere.network/xrpc/com.atproto.repo.listRecords?repo=did:plc:v7jck74ank374heibwj27dd6&collection=network.ionosphere.sounding"

Status

This is the first version. It runs on a single machine with no availability target, so expect outages. The records are published to Ionosphere's own AT Protocol server on that machine, so they are unavailable while it is down. But each record is signed, so any copy someone has kept stays verifiable, and this page stays up regardless. It currently relays aircraft data for the area around Washington, DC, and vessel distress worldwide, as far as aisstream.io's receivers reach. Vessel events have only this one source so far, so they stay at the flash tier. Stations that publish their own receivers' data can join at any time: their reports count as independent observations.

Credits