Geo›Countries›Saudi Arabia›Week of 28 Sep to 4 Oct 2026

Saudi Arabia: what the public records say, 28 Sep to 4 Oct 2026

Signals · now against their own normaldashed line: the normal

InternetRouted IPv4 address spaceRIPE RIS and RouteViews · 7 days, hourly

41,041normal

AirCivil aircraft overheadadsb.lol · 7 days, hourly

80normal

AirMilitary aircraft, Gulfadsb.lol · 7 days, hourly

6counts too small for a ratio

AirMilitary aircraft, Red Seaadsb.lol · 7 days, hourly

0counts too small for a ratio

SeaShip transits, Strait of HormuzIMF PortWatch · 30 days, daily

1counts too small for a ratio

SeaShip transits, Bab el Mandeb StraitIMF PortWatch · 30 days, daily

27normal

GroundFire clusters, Iran Iraq GulfNASA FIRMS · 30 days, daily

508normal

GroundFire clusters, Red Sea YemenNASA FIRMS · 30 days, daily

18normal

Measured by FirmTape's own collectors from public data. A normal needs history before it means anything, so a young series says when it will be ready instead of drawing a line. No chart for a sector means no collector sees that country, not that it is calm.

All Government Air GPS Sea Internet Ground Space AttentionNotable only

3 notable · 0 routine hidden

Sat 3 Oct 2026

04:00GPSSA · Gulf and Strait of Hormuz: GPS interference in 2 new areas, up to 50% of aircraft with degraded position integrityadsb.lol

Fri 2 Oct 2026

20:00GPSSA · Gulf and Strait of Hormuz: GPS interference in 1 new area, up to 25% of aircraft with degraded position integrityadsb.lol

19:00GPSSA · Gulf and Strait of Hormuz: GPS interference in 1 new area, up to 25% of aircraft with degraded position integrityadsb.lol

What this page is not. It does not predict anything and it does not beat the news: almost every record here is published openly and reaches reporters the same minute it reaches this page. Where the slow signals come from. Internet outages, military aviation, emptied airspace, GPS interference and ship traffic are measured on our own collector server and publish only after each has learned its normal. Alerts by email, Telegram or webhook, and the records through an API and MCP, are on the Geo plans. Rows marked backfill came from a source's own history rather than from live collection, so they never count toward how fast we saw something.

Last 30 days

This week5 to 11 Oct11 notable

W4028 Sep to 4 Oct33 notable

W3921 to 27 Sep11 notable W3814 to 20 Sep52 notable

Sources

54 answering0 quiet what each one reads

Show all 54

AMSA22 minAviation Weather Center22 minBarentsWatch2 minCanada52 minCelesTrak1 minCongress1 hCopernicus EMS22 minCouncil of the EU22 minDanish Maritime Authority2 minEASA2 hENTSO-E22 minEU sanctions2 hFAA22 minFAA NAS Status7 minFEMA2 hFederal Register2 hFintraffic Digitraffic2 minGDACS7 minGDELT22 minIAEA2 hIMF PortWatch5 hJapan Coast Guard22 minJapan MOFA7 minMARAD290 hNASA Black Marble1 minNASA FIRMS1 hNGA22 minNOAA SWPC22 minNOAA Tsunami2 minNational Hurricane Center22 minNational Weather Service2 minOFAC22 minPentagon7 minRIPE RIS2 minReliefWeb22 minSafecast2 hSpace-Track1 minSpanish Navy IHM22 minState Dept advisories7 minTaiwan MND1 hTor Metrics5 hUCDP22 minUK FCDO2 minUK Ministry of Defence22 minUK sanctions22 minUS embassy alerts1 minUSCG NAVCEN22 minUSGS2 minWhite House22 minWikipedia edits52 minWikipedia reads2 hadsb.lol0 minadsb.lol0 minadsb.lol0 min

A source that stops answering does not go quiet here. Its rows stop and this list says when it was last heard from, because no data is not the same as nothing happening.

Times are New York (ET), like every page on this site. US federal records are public domain, UK advice is Open Government Licence, GDACS and Wikimedia carry Creative Commons terms, conflict deaths are from the Uppsala Conflict Data Program (UCDP GED Candidate, CC BY 4.0). Every row links to the record it came from and nothing is republished as a bulk feed. This week as JSON (times in UTC, each item marked routine or not; every week)