Lebanon: what the public records say, 19 Oct to 25 Oct 2026

Geo›Countries›Lebanon›Week of 19 Oct to 25 Oct 2026

Signals · now against their own normaldashed line: the normal

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

2,058normal

AirCivil aircraft overheadadsb.lol · 7 days, hourly

12counts too small for a ratio

AirMilitary aircraft, East Medadsb.lol · 7 days, hourly

0counts too small for a ratio

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

1counts too small for a ratio

GroundFire clusters, Levant IsraelNASA FIRMS · 30 days, daily

82normal

GroundNight lights, BeirutNASA Black Marble · 30 days, daily

35.9normal

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

2 notable · 2 routine hidden, show them

Sat 24 Oct 2026

10:32GovernmentLB · Security Alert: U.S. Embassy Beirut – October 24, 2026US embassy alerts

05:23GovernmentLB · Travel Advisory: Lebanon October 2026US embassy alerts

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

W4319 to 25 Oct42 notable

W4212 to 18 Oct11 notable W415 to 11 Oct11 notable

Sources

54 answering3 quiet what each one reads

adsb.lolstale 5 hadsb.lolstale 5 hadsb.lolstale 5 h

Show all 57

AMSA1 hAviation Weather Center2 minBarentsWatch2 minCanada2 minCelesTrak3 minCongress1 hCopernicus EMS32 minCopernicus Sentinel-1 via Planetary Computer2 minCopernicus Sentinel-2 via Planetary Computer2 minCouncil of the EU32 minDanish Maritime Authority1 minEASA1 hENTSO-E1 hEU sanctions1 hFAA2 minFAA NAS Status2 minFEMA1 hFederal Register1 hFintraffic Digitraffic3 minGDACS2 minGDELT32 minIAEA1 hIMF PortWatch7 hJapan Coast Guard1 hJapan MOFA2 minMARAD91 hNASA Black Marble3 minNASA FIRMS1 hNASA FIRMS1 hNGA2 minNOAA SWPC2 minNOAA Tsunami2 minNational Hurricane Center32 minNational Weather Service2 minOFAC32 minPentagon2 minRIPE RIS0 minReliefWeb1 hSafecast1 hSpace-Track2 minSpanish Navy IHM1 hState Dept advisories2 minTaiwan MND1 hTor Metrics1 hUCDP1 hUK FCDO12 minUK Ministry of Defence32 minUK sanctions32 minUS embassy alerts2 minUSCG NAVCEN32 minUSGS2 minWhite House2 minWikipedia edits2 minWikipedia reads1 h

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)