Week 40, 2026 · Sep 21 – Sep 27

Covers Monday Sep 21 00:00 to Monday Sep 28 00:00 UTC.

How to read this: we measure millions of internet routes around the world. Every speed number below is how many milliseconds (thousandths of a second) slower a route ran than its own normal speed, so higher is worse. Each section says whether things got better or worse than last week.

Bharti Airtel Limited’s rough weekthe week’s story

Better than last week. Bharti Airtel Limited is one of the large networks that carry internet traffic between countries. Routes through it ran 31.5 milliseconds slower than normal on average this week (last week: 32.6). 1,734 routes through it were badly slowed (more than 25 milliseconds over normal) at some point. The chart shows how many, hour by hour:

Signed-in customers see the affected routes, the carrier on each side of every changed handoff, and the regional split on the Global fleet view.

The networks that slowed down the most

Large carrier networks, ranked by how much slower than normal their routes ran this week. Big networks get no allowance for their size.

Network	this week, hour by hour	slower than normal	routes badly slowed	last week	compared with last week
SG.GS (Singapore network operator)		46.8 ms	829	46.4 ms	About the same as last week
FLAG Telecom		36.4 ms	273	31.0 ms	Worse than last week
Bharti Airtel Limited		31.5 ms	1,734	32.6 ms	Better than last week
SEACOM		26.5 ms	422	26.3 ms	About the same as last week
TransTelecom		26.4 ms	532	26.7 ms	About the same as last week
Gateway Communications (Belgium)		24.9 ms	2,392	26.1 ms	Better than last week

“Routes badly slowed” counts routes that ran more than 25 milliseconds over normal at some point this week.

1,539 outages and problems reported by companies

Fewer than last week (down 9%). These are problems online services posted on their own status pages. Last week: 1,697.

Online business software (SaaS) had the most problems again, as it usually does.

What tended to break, in providers’ own words: connectivity ×140 · slowness ×93 · auth & login ×78 · elevated errors ×66

Longest problems to fix: University of Nebraska–Lincoln — GlobalProtect VPN under investigation (486 hours, about 20 days); Bit2Me — Aviso de deslistado de MemeCore (M) / Delisting Notice — MemeCore (M) (479 hours, about 20 days); Bit2Me — Aviso de deslistado de Covalent X Token (CXT) / Delisting Notice — Cov (479 hours, about 20 days).

Ground eventsthe physical world, and whether the internet flinched

Ongoing, week 15 of tracking: Iran, the same as last week. People are back online after the months-long shutdown that ended in May, but access is still heavily restricted. A new bill to tighten control of the internet was put to lawmakers on Aug 26. Radio Farda (RFE/RL) reported it was unclear when it would be voted on. Routes into Iran (60 we measure) ran 0.7 milliseconds slower than normal, the same as last week.

We cover earthquakes of magnitude 7.0 or more and storms at the top two disaster alert levels. “Our fleet’s view” is what our own measurements saw, not a damage report.

Subsea watchwhere the internet is wet

For the feedpaste-ready

Every figure derives from SquidGrid’s own measurement fleet and its archive of provider-published incidents; provider self-reports are labeled as such. Provider Assessment Reports carry the per-provider detail. The internet was mostly fine this week. We measured anyway.