Geo›Countries›Yemen›Week of 14 Sep to 20 Sep 2026

Yemen: what the public records say, 14 Sep to 20 Sep 2026

Signals · now against their own normaldashed line: the normal

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

895normal ready 2026-09-23

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

0normal ready 2026-09-30

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

31normal

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

12normal

GroundNight lights, SanaaNASA Black Marble · 30 days, daily

10.8normal 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 · 2 routine, dimmed, hide them

Sun 20 Sep 2026

17:00GroundYE · Yemen, August 2026: 643 deaths in 114 conflict events (12-month median 59)UCDP

Thu 17 Sep 2026

13:01SeaYE · HYDROPAC 2696/26: Piracy Event (Gulf Of Aden. Yemen.)NGA

06:52GroundYE · Yemen, July 2026: 166 deaths in 43 conflict events (12-month median 56)UCDP

Wed 16 Sep 2026

15:00AttentionYE · GDELT conflict events spike: YE (30 events/h vs median 7)GDELT

Tue 15 Sep 2026

06:00AttentionYE · GDELT conflict events spike: YE (27 events/h vs median 7)backfillGDELT

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 Sep53 notable

W377 to 13 Sep22 notable W3631 Aug to 6 Sep10 notable

Sources

50 answering0 quiet what each one reads

Show all 50

Aviation Weather Center15 minBarentsWatch2 minCanada15 minCelesTrak0 minCongress1 hCopernicus EMS45 minCouncil of the EU45 minDanish Maritime Authority3 minEASA1 hENTSO-E1 hEU sanctions1 hFAA15 minFAA NAS Status0 minFEMA1 hFederal Register1 hFintraffic Digitraffic2 minGDACS15 minGDELT45 minIAEA1 hIMF PortWatch7 hJapan MOFA0 minNASA Black Marble2 minNASA FIRMS1 hNGA15 minNOAA SWPC15 minNOAA Tsunami5 minNational Hurricane Center45 minNational Weather Service5 minOFAC45 minPentagon15 minRIPE RIS4 minReliefWeb45 minSafecast1 hSpace-Track1 minState Dept advisories15 minTaiwan MND1 hTor Metrics1 hUCDP45 minUK FCDO5 minUK Ministry of Defence45 minUK sanctions45 minUS embassy alerts0 minUSCG NAVCEN45 minUSGS5 minWhite House15 minWikipedia edits15 minWikipedia reads1 hadsb.lol2 minadsb.lol2 minadsb.lol2 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)