Geo›Countries›Iran›This week

Iran: what the public records say

Signals · now against their own normaldashed line: the normal

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

39,498normal ready 2026-09-23

AirCivil aircraft overheadadsb.lol · 7 days, hourly

2normal ready 2026-09-30

AirMilitary aircraft, Gulfadsb.lol · 7 days, hourly

4normal ready 2026-09-30

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

0normal ready 2026-09-30

GPSAircraft with degraded GPS, Iran Makranadsb.lol · 7 days, hourly

0normal ready 2026-09-30

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

8counts too small for a ratio

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

498normal

GroundNight lights, TehranNASA Black Marble · 30 days, daily

56.6normal ready 2026-10-10

AttentionWikipedia edits, Strait of HormuzWikimedia · 7 days, hourly

0counts too small for a ratio

AttentionWikipedia edits, Persian GulfWikimedia · 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

0 notable · 0 routine, dimmed, hide them

—NoneNothing crossed its normal in this window. Quiet is a reading here, not a gap: the source list below says who answered.

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

W3814 to 20 Sep63 notable W377 to 13 Sep32 notable W3631 Aug to 6 Sep54 notable W3524 to 30 Aug33 notable

Sources

50 answering0 quiet what each one reads

Show all 50

Aviation Weather Center18 minBarentsWatch0 minCanada1 hCelesTrak1 minCongress47 minCopernicus EMS47 minCouncil of the EU47 minDanish Maritime Authority1 minEASA2 hENTSO-E47 minEU sanctions2 hFAA18 minFAA NAS Status3 minFEMA2 hFederal Register2 hFintraffic Digitraffic0 minGDACS33 minGDELT47 minIAEA2 hIMF PortWatch8 hJapan MOFA3 minNASA Black Marble0 minNASA FIRMS47 minNGA18 minNOAA SWPC18 minNOAA Tsunami8 minNational Hurricane Center47 minNational Weather Service8 minOFAC47 minPentagon33 minRIPE RIS1 minReliefWeb47 minSafecast2 hSpace-Track3 minState Dept advisories33 minTaiwan MND47 minTor Metrics2 hUCDP47 minUK FCDO8 minUK Ministry of Defence47 minUK sanctions47 minUS embassy alerts0 minUSCG NAVCEN47 minUSGS8 minWhite House18 minWikipedia edits1 hWikipedia 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)