Where we stand
GPS interference observability
Aviation GPS jamming and spoofing detection across the monitored Flight Information Regions — already worldwide. Live map refreshed daily.
Risk scoring coverage
Risk scoring spans 334 FIRs across multi-source intelligence with backtest-validated methodology — covering weather, geophysical, conflict, and operational signals. Coverage expanded from 25 FIRs at launch to 334 today.
Volcanic ash — airport-level
Real-time aviation colour codes from 6 observatory networks — USGS, INGV, Iceland, Indonesia, Kamchatka and the Smithsonian GVP — plus an independent satellite-thermal feed. Volcanic-ash risk resolves to the specific airports in the affected zone.
Airspace is divided into Flight Information Regions. We publish three honestly separate, independently-measured tiers rather than one blended figure — because “coverage” means different things at different depths:
- 334
- Risk-scored — a full multi-source risk score on demand, refreshed daily. This is our headline coverage figure.
- —
- GPS-observable — a daily GNSS-interference signal only; a lighter observability layer, already worldwide.
Why 334 and not simply “every region on Earth”? There is no single official global count — depending on whether upper (UIR) and oceanic sectors are counted separately, published estimates range from roughly 300 to over 450. Our 334 counts flight information regions on the served surface once each (a FIR and its upper counterpart are one region; airports and simulator-only sectors are excluded), and 256 of them carry an official ICAO boundary polygon. We quote absolute counts rather than a “% of the world” figure precisely because that denominator is genuinely ambiguous.
Now
building- ⟳ Extending depth of coverage beyond the current monitored set
- ⟳ Sharpening regulatory-signal correlation and per-route signal delivery
Next
this year- ○ Expanding the monitored set on partner demand
- ○ Per-route subscriptions and richer partner integrations
- ○ Independently auditable observability for enterprise partners
Later
visionA world where airspace risk is treated as common infrastructure for aviation — continuously available, source-cited, and consistent across operators, insurers, and platforms. A shared reference that complements official channels, never replaces them.
Requested by users
community · under reviewNothing under community review right now — yours could be first.
Votes are noted, not displayed — they weigh into prioritisation together with verified customer votes from the Console.
Don't see what you need? Request it
Reviewed by a human before it appears above. No dates promised — statuses are honest.
Already a Console or API user? Request from your dashboard — verified requests carry more weight.
Themes describe direction, not commitments. Quarter targets and specific items are curated for partner conversations rather than published — we publish only what we are confident in honestly committing to.
Recently
what's happened · newest firstOfficial client libraries are published: @flysafe/api on npm (zero-dependency, TypeScript types) and flysafe-api on PyPI (Python 3.8+). Route risk on engine v1/v2, introspection, webhooks and signature verification. MIT-licensed.
Details
FlySafe client libraries are now on the public registries:
- JavaScript / TypeScript — `@flysafe/api` on npm. Zero runtime dependencies, ships TypeScript types, runs on Node 18+, browsers, Cloudflare Workers and Deno.
- Python — `flysafe-api` on PyPI. Python 3.8+, a single
requestsdependency.
npm install @flysafe/api
pip install flysafe-api
Both clients cover the full public surface: route risk on engine v1 and v2 (including reroute analysis and adjusted_score), FIR scores and signals, self-serve introspection (/v2/me/* usage and query history), webhook management, and local HMAC verification of webhook signatures — plus retries with exponential backoff out of the box.
Honest versioning note: the current release is 0.2.x. The clients are small by design (~200 lines each) and smoke-tested against the live API on every release, but we will not call them 1.0 until the test suite we want is in place. Semver applies — anything breaking lands behind a major bump and a changelog entry here.
Get a free sandbox key on the API page and you can make your first scored request minutes from now.
Show full history
Want this product applied to your routes or FIRs?
Partner requests directly influence which FIRs and capabilities we prioritise next. We read every message and respond personally.
This is a public capability-level view. Internal details — exact dependencies, vendor selections, effort estimates, and trade-offs — are intentionally not exposed. Item-level delivery history is curated for partner conversations. We publish only what we are confident in honestly committing to.