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

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

129,460normal ready 2026-09-23

AirCivil aircraft overheadadsb.lol · 7 days, hourly

87normal ready 2026-09-30

AirPLA aircraft around TaiwanTaiwan MND · 30 days, daily

5normal ready 2026-10-08

GPSAircraft with degraded GPS, Taiwanadsb.lol · 7 days, hourly

0normal ready 2026-09-30

SeaShip transits, Taiwan StraitIMF PortWatch · 30 days, daily

226normal

SeaShip transits, Luzon StraitIMF PortWatch · 30 days, daily

107normal

SeaPLA ships around TaiwanTaiwan MND · 30 days, daily

11normal ready 2026-10-08

GroundFire clusters, Taiwan StraitNASA FIRMS · 30 days, daily

9counts too small for a ratio

GroundNight lights, TaipeiNASA Black Marble · 30 days, daily

49.1normal ready 2026-10-09

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

1 notable · 0 routine hidden

Thu 17 Sep 2026

21:00AirTW CN · PLA activity around Taiwan: 28 aircraft sorties (24 across the median line), 7 navy ships, against a normal of 8 sortiesTaiwan MND

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

W377 to 13 Sep10 notable W3631 Aug to 6 Sep10 notable W3524 to 30 Aug30 notable

Sources

50 answering0 quiet what each one reads

Show all 50

Aviation Weather Center10 minBarentsWatch0 minCanada40 minCelesTrak2 minCongress40 minCopernicus EMS40 minCouncil of the EU40 minDanish Maritime Authority2 minEASA40 minENTSO-E40 minEU sanctions40 minFAA10 minFAA NAS Status10 minFEMA40 minFederal Register40 minFintraffic Digitraffic0 minGDACS40 minGDELT40 minIAEA40 minIMF PortWatch6 hJapan MOFA10 minNASA Black Marble0 minNASA FIRMS40 minNGA10 minNOAA SWPC10 minNOAA Tsunami0 minNational Hurricane Center40 minNational Weather Service0 minOFAC40 minPentagon40 minRIPE RIS4 minReliefWeb40 minSafecast40 minSpace-Track0 minState Dept advisories40 minTaiwan MND40 minTor Metrics40 minUCDP40 minUK FCDO0 minUK Ministry of Defence40 minUK sanctions40 minUS embassy alerts1 minUSCG NAVCEN40 minUSGS0 minWhite House10 minWikipedia edits40 minWikipedia reads40 minadsb.lol1 minadsb.lol1 minadsb.lol1 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)