Geo›Countries›Yemen›Week of 28 Sep to 4 Oct 2026

Yemen: 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

894normal

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

0counts too small for a ratio

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

27normal

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

18normal

GroundNight lights, SanaaNASA Black Marble · 30 days, daily

17.7normal ready 2026-10-10

AttentionWikipedia edits, Red Sea crisisWikimedia · 7 days, hourly

0counts too small for a ratio

AttentionWikipedia edits, Bab-el-MandebWikimedia · 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 hidden

Sat 3 Oct 2026

20:00AttentionYE · GDELT conflict events spike: YE (25 events/h vs median 1)GDELT

06:00AttentionYE · GDELT conflict events spike: YE (25 events/h vs median 1)GDELT

Fri 2 Oct 2026

06:00AttentionYE · GDELT conflict events spike: YE (32 events/h vs median 1)GDELT

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 Sep32 notable W3814 to 20 Sep53 notable W377 to 13 Sep22 notable

Sources

54 answering0 quiet what each one reads

Show all 54

AMSA25 minAviation Weather Center25 minBarentsWatch1 minCanada55 minCelesTrak3 minCongress1 hCopernicus EMS25 minCouncil of the EU25 minDanish Maritime Authority1 minEASA2 hENTSO-E25 minEU sanctions2 hFAA25 minFAA NAS Status10 minFEMA2 hFederal Register2 hFintraffic Digitraffic1 minGDACS10 minGDELT25 minIAEA2 hIMF PortWatch5 hJapan Coast Guard25 minJapan MOFA10 minMARAD290 hNASA Black Marble3 minNASA FIRMS1 hNGA25 minNOAA SWPC25 minNOAA Tsunami5 minNational Hurricane Center25 minNational Weather Service5 minOFAC25 minPentagon10 minRIPE RIS0 minReliefWeb25 minSafecast2 hSpace-Track3 minSpanish Navy IHM25 minState Dept advisories10 minTaiwan MND1 hTor Metrics5 hUCDP25 minUK FCDO5 minUK Ministry of Defence25 minUK sanctions25 minUS embassy alerts1 minUSCG NAVCEN25 minUSGS5 minWhite House25 minWikipedia edits55 minWikipedia reads2 hadsb.lol3 minadsb.lol3 minadsb.lol3 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)