Internet quality by location

Measured period 2026-10-06 23:25 to 00:25 EDT · one measurement per second per location

At a glance

▲now  As of 00:10–00:24 EDT, ending 2 minutes ago, 2 of 10 locations were over the 1.0% loss threshold: 255, 371.

255 watch371 watch355 clean125 clean212 clean629 clean630 clean729 clean76 cleanCONTROL clean

▲last 24h  7 location(s) went over the 1.0% threshold at some point in the last 24 hours: 629 (12h), 630 (12h), 125 (11h), 729 (9h). Worst single hour 6.2% at 629.

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
25572 minutes agooutside 0.997% - agrees within 1.0 point
37113 minutes agooutside 0.839% - agrees within 1.0 point
35564 minutes agooutside 0.934% - agrees within 1.0 point
6301240 minutes agono outside data
125114.4 hours agooutside 0.0% - agrees within 1.0 point
212015.1 hours agooutside 0.0% - agrees within 1.0 point
629121.8 hours agooutside 0.042% - agrees within 1.0 point
72994.4 hours agooutside 0.0% - agrees within 1.0 point
7603.3 hours agooutside 0.0% - agrees within 1.0 point

One block per hour from 01:00 EDT onwards. Green is at or below 1.0% loss, amber above it, orange above 5.0%, red above 10.0%, grey is unmeasured. Hover a block for its figure.
Independent view is the same window measured from a machine on an unrelated datacentre connection, which pings each location from the public internet instead of asking that location's own equipment to send the test. It shares none of the main monitor's machinery, so it is a running check on it. A slightly higher figure there is expected, because that path is longer. A materially LOWER figure would mean the loss is being produced at or near the measurement rather than on the line.

Current conditions — 00:10–00:24 EDT

▲degraded  As of 00:10–00:24 EDT, ending 2 minutes ago, 2 of 10 locations were over the 1.0% loss threshold: 255, 371.

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
255▲watch1.56%14.4714/89915
371▲watch1.11%14.5710/89915
355✓clean0.67%16.696/90015
125✓clean0.0%15.650/90015
212✓clean0.0%4.650/90015
629✓clean0.0%16.610/90015
630✓clean0.0%17.790/89915
729✓clean0.0%14.060/90015
76✓clean0.0%12.850/90015
CONTROL✓clean0.0%1.20/90015

Measurement runs continuously, one sample per second per location, and this page is republished every 5 minutes. Page built 00:25 EDT. Newest measured minute on record: 00:24 EDT, 2 minutes ago. The measurement period summarised below runs up to 00:25 EDT and is still going - that is its latest sample, less than a minute ago, not an end. This page reloads itself every 10 minutes.

The measurement period — 23:25–00:25 EDT on 2026-10-06

▲degraded  During 23:25–00:25 EDT on 2026-10-06, 1 of 9 locations lost more packets than the threshold allows: 255.

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: 3600 seconds, one sample per second per location. A single lost second moves a location's loss figure by 0.028 percentage points, so small percentages rest on few events. Graphs below cover a longer window and are labelled separately.

Problems found during 23:25–00:25 EDT on 2026-10-06

SeverityWhereWhat it means
MEDIUM255dropped more packets over the measured period than the threshold allows
MEDIUMshared carrier equipment, group Aseveral locations sharing one piece of carrier equipment lost packets in the same seconds, so the fault is upstream of all of them
9 note(s) about the measurement itself, not problems with any location
SeverityWhereWhat it means
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 6 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 6 hours, 2026-10-06 18:25 to 2026-10-07 00:25 Eastern, across every measurement run in that window. 99.7% of those hours carry data. Measurement is continuous now, so that figure climbs towards 100% as the day goes on; the gaps are earlier periods when measurement ran in short scheduled sessions instead. An unmeasured period is not a quiet period.

25514–16 ms · 0% of the window unmeasured
37113–17 ms · 0% of the window unmeasured
35513–19 ms · 0% of the window unmeasured
63016–37 ms · 0% of the window unmeasured
12514–40 ms · 0% of the window unmeasured
2124–5 ms · 0% of the window unmeasured
62915–42 ms · 0% of the window unmeasured
72913–41 ms · 0% of the window unmeasured
7611–14 ms · 0% of the window unmeasured

Each location during 23:25–00:25 EDT on 2026-10-06

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
255▲watch1.2%2.67%14.5420.6552.52
371✓clean0.98%2.0%14.722.792.56
355✓clean0.87%1.67%16.4425.89157.58
630✓clean0.03%0.33%17.1528.5288.55
125✓clean0.0%0.0%15.6522.1840.05
212✓clean0.0%0.0%4.645.8417.68
629✓clean0.0%0.0%16.4830.181.07
729✓clean0.0%0.0%14.2121.2362.64
76✓clean0.0%0.0%12.5416.2245.17

Every interruption during 23:25–00:25 EDT on 2026-10-06

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

TimeLocationKindSeconds
00:00:02371MICRO_DROP1
00:00:14371MICRO_DROP1
00:00:27355MICRO_DROP1
00:00:32255MICRO_DROP1
00:00:57355MICRO_DROP1
00:01:10255MICRO_DROP1
00:01:28355MICRO_DROP1
00:02:55371MICRO_DROP1
00:04:33629SLOWDOWN26
00:04:34371MICRO_DROP1
00:04:54255MICRO_DROP1
00:05:24355MICRO_DROP1
00:05:51355MICRO_DROP1
00:06:14355MICRO_DROP1
00:06:39371MICRO_DROP1
00:06:45630SLOWDOWN47
00:07:21255MICRO_DROP1
00:08:55255MICRO_DROP1
00:08:59355MICRO_DROP1
00:09:48355MICRO_DROP1
00:13:54371MICRO_DROP1
00:14:27255MICRO_DROP1
00:14:37255MICRO_DROP1
00:14:44355MICRO_DROP1
00:14:48371MICRO_DROP1
00:15:22355MICRO_DROP1
00:15:24255MICRO_DROP1
00:15:45371MICRO_DROP1
00:16:04371MICRO_DROP1
00:16:21255MICRO_DROP1
00:16:24255MICRO_DROP1
00:16:40355MICRO_DROP1
00:16:44371MICRO_DROP1
00:17:04255MICRO_DROP1
00:17:40255MICRO_DROP1
00:17:50355MICRO_DROP1
00:17:52255MICRO_DROP1
00:18:44371MICRO_DROP1
00:19:30255MICRO_DROP1
00:19:42371MICRO_DROP1
00:20:17355MICRO_DROP1
00:21:03371MICRO_DROP1
00:21:05255MICRO_DROP1
00:22:21355MICRO_DROP1
00:23:28255MICRO_DROP1
00:23:32371MICRO_DROP1
00:23:45255MICRO_DROP1
00:23:53255MICRO_DROP1
00:23:53371MICRO_DROP1
00:24:07255MICRO_DROP1
00:25:04355MICRO_DROP1
00:25:13355MICRO_DROP1
23:26:38371MICRO_DROP1
23:26:47371MICRO_DROP1
23:27:43255MICRO_DROP1
23:28:29371MICRO_DROP1
23:28:51371MICRO_DROP1
23:29:35355MICRO_DROP1
23:31:19255MICRO_DROP1
23:32:07371MICRO_DROP1
23:32:33355MICRO_DROP1
23:32:36371MICRO_DROP1
23:33:15255MICRO_DROP1
23:33:23255MICRO_DROP1
23:33:34629SLOWDOWN11
23:34:58355MICRO_DROP1
23:35:30371MICRO_DROP1
23:35:39355MICRO_DROP1
23:35:39371MICRO_DROP1
23:36:41255MICRO_DROP1
23:36:47355MICRO_DROP1
23:36:48371MICRO_DROP1
23:36:58255MICRO_DROP1
23:37:27371MICRO_DROP1
23:37:30371MICRO_DROP1
23:37:45371MICRO_DROP1
23:39:47255MICRO_DROP1
23:40:25355MICRO_DROP1
23:40:31255MICRO_DROP1
23:40:38255MICRO_DROP1
23:41:56371MICRO_DROP1
23:42:25371MICRO_DROP1
23:42:33255MICRO_DROP1
23:43:22355MICRO_DROP1
23:43:24255MICRO_DROP1
23:45:01255MICRO_DROP1
23:45:56371MICRO_DROP1
23:46:25355MICRO_DROP1
23:46:29630MICRO_DROP1
23:46:39371MICRO_DROP1
23:46:41255MICRO_DROP1
23:48:45255MICRO_DROP1
23:48:45355MICRO_DROP1
23:48:54255MICRO_DROP1
23:50:13355MICRO_DROP1
23:50:16255MICRO_DROP1
23:50:22255MICRO_DROP1
23:50:32255MICRO_DROP1
23:50:49255MICRO_DROP1
23:53:02371MICRO_DROP1
23:53:10371MICRO_DROP1
23:53:54371MICRO_DROP1
23:54:31355MICRO_DROP1
23:54:37255MICRO_DROP1
23:55:19355MICRO_DROP1
23:55:26371MICRO_DROP1
23:55:33255MICRO_DROP1
23:56:15355MICRO_DROP1
23:56:32255MICRO_DROP1
23:56:47255MICRO_DROP1
23:57:04355MICRO_DROP1
23:58:26255MICRO_DROP1
23:59:11355MICRO_DROP1

Terms

clean means loss at or below 1 per cent, watch above 1 and up to 5, degraded above 5 and up to 10, failing above 10. 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. Typical ms is the middle response time. Slowest 1 in 20 is the 95th percentile. Worst 5 min is the highest loss over any five consecutive minutes in the period, which catches loss that is concentrated rather than spread evenly. The independent reference is a machine on an unrelated datacentre connection running the same test, so a bad moment at the address being pinged is not mistaken for a fault at these locations. MICRO_DROP is one or two lost seconds, SHORT_FAILURE three to twenty-nine, OUTAGE thirty or more, and SLOWDOWN is at least ten seconds much slower than that location's own median for the measured period - not against its long-run history.