United Arab Emirates: what the public records say, 5 Oct to 11 Oct 2026

Geo›Countries›United Arab Emirates›Week of 5 Oct to 11 Oct 2026

Signals · now against their own normaldashed line: the normal

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

24,555normal

AirCivil aircraft overheadadsb.lol · 7 days, hourly

175normal

AirMilitary aircraft, Gulfadsb.lol · 7 days, hourly

5counts too small for a ratio

GPSAircraft with degraded GPS, Gulf Hormuzadsb.lol · 7 days, hourly

0counts too small for a ratio

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

4counts too small for a ratio

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

438normal

AttentionWikipedia edits, Strait of HormuzWikimedia · 7 days, hourly

0counts too small for a ratio

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, dimmed, hide them

Sun 11 Oct 2026

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

Fri 9 Oct 2026

13:00GPSAE SA · Gulf and Strait of Hormuz: GPS interference in 2 new areas, up to 67% of aircraft with degraded position integrityadsb.lol

Thu 8 Oct 2026

15:48GovernmentAE · Security Alert: U.S. Mission United Arab Emirates – October 8, 2026”.US embassy alerts

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

W415 to 11 Oct33 notable

W4028 Sep to 4 Oct88 notable W3921 to 27 Sep21 notable W3814 to 20 Sep21 notable

Sources

54 answering0 quiet what each one reads

Show all 54

AMSA6 minAviation Weather Center6 minBarentsWatch2 minCanada6 minCelesTrak3 minCongress36 minCopernicus EMS6 minCouncil of the EU6 minDanish Maritime Authority1 minEASA6 minENTSO-E6 minEU sanctions6 minFAA6 minFAA NAS Status6 minFEMA6 minFederal Register6 minFintraffic Digitraffic2 minGDACS6 minGDELT6 minIAEA6 minIMF PortWatch3 hJapan Coast Guard6 minJapan MOFA6 minMARAD456 hNASA Black Marble1 minNASA FIRMS1 hNGA6 minNOAA SWPC6 minNOAA Tsunami6 minNational Hurricane Center6 minNational Weather Service6 minOFAC6 minPentagon6 minRIPE RIS2 minReliefWeb6 minSafecast6 minSpace-Track2 minSpanish Navy IHM6 minState Dept advisories6 minTaiwan MND1 hTor Metrics3 hUCDP6 minUK FCDO6 minUK Ministry of Defence6 minUK sanctions6 minUS embassy alerts0 minUSCG NAVCEN6 minUSGS6 minWhite House6 minWikipedia edits6 minWikipedia reads6 minadsb.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)