South Korea: what the public records say, 21 Sep to 27 Sep 2026

Geo›Countries›South Korea›Week of 21 Sep to 27 Sep 2026

Signals · now against their own normaldashed line: the normal

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

419,150normal

AirCivil aircraft overheadadsb.lol · 7 days, hourly

580.33x normal

AirMilitary aircraft, Koreaadsb.lol · 7 days, hourly

0counts too small for a ratio

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

0counts too small for a ratio

SeaShip transits, Korea StraitIMF PortWatch · 30 days, daily

220normal

GroundFire clusters, KoreaNASA FIRMS · 30 days, daily

542.04x normal

AttentionWikipedia edits, Korean Demilitarized ZoneWikimedia · 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 · 1 routine, dimmed, hide them

Sun 27 Sep 2026

12:46SpaceKR · Reentry: OBJECT D (payload, South Korea) on 2026-09-24CelesTrak

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 Oct66 notable W4028 Sep to 4 Oct66 notable

W3921 to 27 Sep10 notable

W3814 to 20 Sep99 notable

Sources

54 answering0 quiet what each one reads

Show all 54

AMSA7 minAviation Weather Center7 minBarentsWatch3 minCanada7 minCelesTrak0 minCongress37 minCopernicus EMS7 minCouncil of the EU7 minDanish Maritime Authority2 minEASA7 minENTSO-E7 minEU sanctions7 minFAA7 minFAA NAS Status7 minFEMA7 minFederal Register7 minFintraffic Digitraffic3 minGDACS7 minGDELT7 minIAEA7 minIMF PortWatch3 hJapan Coast Guard7 minJapan MOFA7 minMARAD456 hNASA Black Marble2 minNASA FIRMS1 hNGA7 minNOAA SWPC7 minNOAA Tsunami7 minNational Hurricane Center7 minNational Weather Service7 minOFAC7 minPentagon7 minRIPE RIS3 minReliefWeb7 minSafecast7 minSpace-Track3 minSpanish Navy IHM7 minState Dept advisories7 minTaiwan MND1 hTor Metrics3 hUCDP7 minUK FCDO7 minUK Ministry of Defence7 minUK sanctions7 minUS embassy alerts1 minUSCG NAVCEN7 minUSGS7 minWhite House7 minWikipedia edits7 minWikipedia reads7 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)