Internet quality by location

Measured period 2026-10-03 17:31 to 18:25 EDT · one measurement per second per location

Current conditions — 18:09–18:23 EDT

✓clean  As of 18:09–18:23 EDT, ending 2 minutes ago, all 9 locations were clean.

The most recent measured minutes on record. This answers "what is it doing now", as distinct from the measurement period summarised below.

LocationStateLossTypical msLost / sentMinutes of data
76✓clean0.22%12.752/90015
355✓clean0.0%13.970/90015
255✓clean0.0%14.50/90015
212✓clean0.0%4.730/90015
629✓clean0.0%19.870/90015
630✓clean0.0%18.150/90015
371✓clean0.0%13.480/90015
125✓clean0.0%15.380/90015
729✓clean0.0%13.560/90015

A measurement runs automatically every hour and republishes this page. Page built 18:25 EDT. Newest measured minute on record: 18:23 EDT, 2 minutes ago. The measurement period summarised below ended 18:25 EDT, less than a minute ago. This page reloads itself every 10 minutes.

The measurement period — 17:31–18:25 EDT on 2026-10-03

▲watch  During 17:31–18:25 EDT on 2026-10-03, no location breached a threshold; some showed minor loss.

Each location's internet connection is tested once per second by sending a small packet to a public internet address and waiting for the reply. A missing reply means a packet was lost somewhere between that location and the internet.

Measured period: 3217 seconds, one sample per second per location. A single lost second moves a location's loss figure by 0.031 percentage points, so small percentages rest on few events. Graphs below cover a longer window and are labelled separately.

Problems found during 17:31–18:25 EDT on 2026-10-03

SeverityWhereWhat it means
MEDIUM255loss was concentrated in one five-minute stretch
INFOindependent referencethe independent reference also lost packets, so some loss belongs to the wider internet
INFO125not enough history yet to compare this location against its own normal
INFO212not enough history yet to compare this location against its own normal
INFO255not enough history yet to compare this location against its own normal
INFO355not enough history yet to compare this location against its own normal
INFO371not enough history yet to compare this location against its own normal
INFO629not enough history yet to compare this location against its own normal
INFO630not enough history yet to compare this location against its own normal
INFO729not enough history yet to compare this location against its own normal
INFO76not enough history yet to compare this location against its own normal

Each location over the last 72 hours

One panel per location. The line is the median response time in each slice; rising means slower. The strip underneath marks slices in which packets were lost. Breaks in the line are periods with no measurement, never drawn across. Each panel is scaled to its own range, printed beside its name.

Covers the last 72 hours, 2026-09-30 18:25 to 2026-10-03 18:25 Eastern, across every measurement run in that window. 8.0% of those hours carry data, because measurement runs in discrete sessions rather than continuously. An unmeasured period is not a quiet period.

25514–15 ms · 92% of the window unmeasured
35514–16 ms · 92% of the window unmeasured
7612–13 ms · 92% of the window unmeasured
12515–17 ms · 92% of the window unmeasured
2124–5 ms · 92% of the window unmeasured
37113–15 ms · 92% of the window unmeasured
62916–21 ms · 92% of the window unmeasured
63016–19 ms · 92% of the window unmeasured
72914–15 ms · 92% of the window unmeasured

Each location during 17:31–18:25 EDT on 2026-10-03

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
255✓clean0.93%10.0%14.6420.4356.09
355✓clean0.12%0.67%14.1421.9258.2
76✓clean0.12%0.33%12.6616.4365.63
125✓clean0.0%0.0%15.4124.147.68
212✓clean0.0%0.0%4.685.9218.23
371✓clean0.0%0.0%13.7719.23131.59
629✓clean0.0%0.0%16.840.2758.9
630✓clean0.0%0.0%17.7739.9857.29
729✓clean0.0%0.0%13.8219.2735.26

Every interruption during 17:31–18:25 EDT on 2026-10-03

Includes one-second blips, which are harmless alone but indicate an unsteady connection. Times are Eastern.

TimeLocationKindSeconds
17:35:03355MICRO_DROP1
17:38:1376MICRO_DROP1
17:38:40355SLOWDOWN11
17:40:47355SLOWDOWN21
17:40:49355MICRO_DROP1
17:43:19355MICRO_DROP1
17:45:1176MICRO_DROP1
17:46:55355MICRO_DROP1
17:46:57355SLOWDOWN11
17:49:47355SLOWDOWN16
17:54:56629SLOWDOWN20
17:55:51629SLOWDOWN39
17:56:36629SLOWDOWN14
17:57:02629SLOWDOWN13
17:57:46255MICRO_DROP1
17:57:53255SHORT_FAILURE3
17:58:00255MICRO_DROP1
17:58:51255MICRO_DROP1
17:58:58255MICRO_DROP1
17:59:30255SHORT_FAILURE3
17:59:44255MICRO_DROP1
17:59:53255MICRO_DROP2
18:00:03255MICRO_DROP1
18:00:05255MICRO_DROP1
18:00:15255MICRO_DROP1
18:00:17255MICRO_DROP2
18:00:44255MICRO_DROP2
18:00:53255MICRO_DROP2
18:01:00255MICRO_DROP1
18:01:13255MICRO_DROP2
18:01:43255MICRO_DROP1
18:01:53255MICRO_DROP1
18:02:02255MICRO_DROP2
18:02:12255MICRO_DROP1
18:05:08630SLOWDOWN29
18:09:5876MICRO_DROP1
18:17:1376MICRO_DROP1
18:22:38629SLOWDOWN20
18:23:11629SLOWDOWN18
18:23:25630SLOWDOWN14

Terms

Minutes of data is how many one-minute summaries a current-conditions row is computed from, out of the 15 most recent available - 10 means the figure rests on 600 tests, 1 means it rests on 60. Loss is the share of once-per-second tests that got no reply; zero is normal. Typical ms is the middle response time. Slowest 1 in 20 is the 95th percentile. MICRO_DROP is one or two lost seconds, SHORT_FAILURE three to twenty-nine, OUTAGE thirty or more, and SLOWDOWN at least ten seconds much slower than that location's own normal.