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

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

20,306normal ready 2026-09-23

GroundFire clusters, India PakistanNASA FIRMS · 30 days, daily

441.76x normal

GroundNight lights, KarachiNASA Black Marble · 30 days, daily

62.9normal 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

5 notable · 3 routine, dimmed, hide them

Sun 20 Sep 2026

17:00GroundPK · Pakistan, August 2026: 536 deaths in 151 conflict events (12-month median 366)UCDP

Sat 19 Sep 2026

03:00AttentionPK · GDELT conflict events spike: PK (25 events/h vs median 4)GDELT

Fri 18 Sep 2026

14:02SeaPK · HYDROPAC 2716/26: Hazardous Operations (Arabian Sea. Pakistan.)NGA

10:32SeaPK · HYDROPAC 2712/26: Hazardous Operations (Arabian Sea. Pakistan.)NGA

09:00AttentionPK · GDELT conflict events spike: PK (37 events/h vs median 3.5)GDELT

Thu 17 Sep 2026

13:00AttentionPK · GDELT conflict events spike: PK (25 events/h vs median 3)GDELT

06:52GroundPK · Pakistan, July 2026: 744 deaths in 194 conflict events (12-month median 345)UCDP

Mon 14 Sep 2026

23:00AttentionPK · GDELT conflict events spike: PK (38 events/h vs median 3)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 Sep85 notable

W3631 Aug to 6 Sep10 notable W3524 to 30 Aug20 notable W3417 to 23 Aug10 notable

Sources

50 answering0 quiet what each one reads

Show all 50

Aviation Weather Center13 minBarentsWatch0 minCanada13 minCelesTrak2 minCongress1 hCopernicus EMS43 minCouncil of the EU43 minDanish Maritime Authority1 minEASA1 hENTSO-E1 hEU sanctions1 hFAA13 minFAA NAS Status13 minFEMA1 hFederal Register1 hFintraffic Digitraffic0 minGDACS13 minGDELT43 minIAEA1 hIMF PortWatch7 hJapan MOFA13 minNASA Black Marble0 minNASA FIRMS1 hNGA13 minNOAA SWPC13 minNOAA Tsunami3 minNational Hurricane Center43 minNational Weather Service3 minOFAC43 minPentagon13 minRIPE RIS2 minReliefWeb43 minSafecast1 hSpace-Track3 minState Dept advisories13 minTaiwan MND1 hTor Metrics1 hUCDP43 minUK FCDO3 minUK Ministry of Defence43 minUK sanctions43 minUS embassy alerts1 minUSCG NAVCEN43 minUSGS3 minWhite House13 minWikipedia edits13 minWikipedia reads1 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)