Internet quality by location

Measured period 2026-10-07 01:40 to 02:40 EDT · one measurement per second per location

At a glance

▲now  As of 02:25–02:39 EDT, ending 2 minutes ago, 1 of 10 locations were over the 1.0% loss threshold: 255.

255 degraded355 clean371 clean630 clean125 clean212 clean629 clean729 clean76 cleanCONTROL clean

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

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
25592 minutes agooutside 3.203% - agrees within 1.0 point
35553 minutes agooutside 1.107% - agrees within 1.0 point
37126 minutes agooutside 1.01% - agrees within 1.0 point
630126 minutes agono outside data
6291219 minutes agooutside 0.051% - agrees within 1.0 point
1251119 minutes agooutside 0.006% - agrees within 1.0 point
212017.3 hours agooutside 0.0% - agrees within 1.0 point
72996.6 hours agooutside 0.0% - agrees within 1.0 point
7605.5 hours agooutside 0.0% - agrees within 1.0 point

One block per hour from 03: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 — 02:25–02:39 EDT

▲degraded  As of 02:25–02:39 EDT, ending 2 minutes ago, 1 of 10 locations were over the 1.0% loss threshold: 255.

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▲degraded9.01%13.8781/89915
355✓clean1.0%18.399/90015
371✓clean0.44%15.184/89915
630✓clean0.11%16.651/90015
125✓clean0.0%13.690/89915
212✓clean0.0%4.610/90015
629✓clean0.0%17.090/89915
729✓clean0.0%13.410/89915
76✓clean0.0%12.740/89915
CONTROL✓clean0.0%1.20/89915

Measurement runs continuously, one sample per second per location, and this page is republished every 5 minutes. Page built 02:40 EDT. Newest measured minute on record: 02:39 EDT, 2 minutes ago. The measurement period summarised below runs up to 02:40 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 — 01:40–02:40 EDT on 2026-10-07

▲degraded  During 01:40–02:40 EDT on 2026-10-07, 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 01:40–02:40 EDT on 2026-10-07

SeverityWhereWhat it means
MEDIUM255dropped more packets over the measured period than the threshold allows
MEDIUM255loss was concentrated in one five-minute stretch
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 20:40 to 2026-10-07 02:40 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.

25513–31 ms · 0% of the window unmeasured
35515–20 ms · 0% of the window unmeasured
37113–18 ms · 0% of the window unmeasured
63015–37 ms · 0% of the window unmeasured
62915–38 ms · 0% of the window unmeasured
12513–29 ms · 0% of the window unmeasured
2124–5 ms · 0% of the window unmeasured
72913–18 ms · 0% of the window unmeasured
7611–16 ms · 0% of the window unmeasured

Each location during 01:40–02:40 EDT on 2026-10-07

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
255▲watch3.22%12.33%14.4424.4754.73
355✓clean0.98%2.0%18.1532.33133.36
371✓clean0.5%1.33%15.0224.2498.5
630✓clean0.14%0.67%17.2431.277.97
629✓clean0.06%0.67%16.8634.9778.54
125✓clean0.03%0.33%14.9722.5448.57
212✓clean0.0%0.0%4.665.8312.84
729✓clean0.0%0.0%13.9220.6764.58
76✓clean0.0%0.0%12.5315.9631.77

Every interruption during 01:40–02:40 EDT on 2026-10-07

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

TimeLocationKindSeconds
01:41:05255MICRO_DROP1
01:41:21355MICRO_DROP1
01:41:24255MICRO_DROP1
01:42:06255MICRO_DROP1
01:42:13371MICRO_DROP1
01:43:11355MICRO_DROP1
01:43:21355MICRO_DROP1
01:43:47255MICRO_DROP1
01:44:22255MICRO_DROP1
01:44:51255MICRO_DROP1
01:45:26371MICRO_DROP1
01:45:31355MICRO_DROP1
01:46:38371MICRO_DROP1
01:48:05355MICRO_DROP1
01:48:13355MICRO_DROP1
01:49:27255MICRO_DROP1
01:49:47355MICRO_DROP1
01:50:21255MICRO_DROP2
01:51:39355MICRO_DROP1
01:52:49255MICRO_DROP1
01:54:03371MICRO_DROP1
01:54:08355MICRO_DROP1
01:54:10371MICRO_DROP1
01:54:11255MICRO_DROP1
01:54:18255MICRO_DROP1
01:55:09255MICRO_DROP1
01:55:48371MICRO_DROP1
01:55:55355MICRO_DROP1
01:56:46371MICRO_DROP1
01:56:52355MICRO_DROP1
01:57:07630MICRO_DROP1
01:57:19630MICRO_DROP1
01:58:02255MICRO_DROP1
02:00:46629SLOWDOWN32
02:00:55255MICRO_DROP1
02:01:01255MICRO_DROP1
02:01:05355MICRO_DROP1
02:01:14355MICRO_DROP2
02:01:15371MICRO_DROP1
02:01:50630SLOWDOWN16
02:02:26255MICRO_DROP1
02:02:50355MICRO_DROP1
02:02:57255MICRO_DROP1
02:03:02355MICRO_DROP1
02:05:02371MICRO_DROP1
02:05:26355MICRO_DROP1
02:06:39255MICRO_DROP1
02:06:56355MICRO_DROP1
02:07:25355MICRO_DROP1
02:08:01355MICRO_DROP1
02:08:04255MICRO_DROP1
02:08:41255MICRO_DROP1
02:09:26630MICRO_DROP1
02:09:28355MICRO_DROP1
02:09:32255MICRO_DROP1
02:10:20371MICRO_DROP1
02:10:33255MICRO_DROP1
02:10:42630MICRO_DROP1
02:10:55255MICRO_DROP1
02:11:14355MICRO_DROP1
02:11:16255MICRO_DROP1
02:12:49355MICRO_DROP1
02:14:10355MICRO_DROP1
02:14:20255MICRO_DROP1
02:14:39255MICRO_DROP1
02:16:20255MICRO_DROP1
02:17:11371MICRO_DROP1
02:18:34355MICRO_DROP1
02:18:50355MICRO_DROP1
02:20:38371MICRO_DROP1
02:20:45630SLOWDOWN19
02:21:12255MICRO_DROP2
02:21:20125SLOWDOWN16
02:21:47255MICRO_DROP1
02:22:39125MICRO_DROP1
02:22:49629MICRO_DROP2
02:22:52371MICRO_DROP1
02:23:49255MICRO_DROP1
02:24:14255MICRO_DROP1
02:24:52255MICRO_DROP1
02:25:25255MICRO_DROP1
02:25:27255MICRO_DROP2
02:25:31255MICRO_DROP1
02:25:33255MICRO_DROP1
02:25:33355MICRO_DROP1
02:25:35255MICRO_DROP1
02:25:52255MICRO_DROP1
02:26:06255MICRO_DROP1
02:26:10255MICRO_DROP1
02:26:22255MICRO_DROP1
02:26:40255MICRO_DROP1
02:26:41355MICRO_DROP1
02:26:43255MICRO_DROP1
02:26:55255MICRO_DROP2
02:27:12255MICRO_DROP1
02:27:18255MICRO_DROP1
02:27:30255MICRO_DROP1
02:27:33255MICRO_DROP1
02:27:37255MICRO_DROP1
02:27:41255MICRO_DROP1
02:27:53355MICRO_DROP1
02:27:54255MICRO_DROP1
02:28:04255MICRO_DROP1
02:28:07255MICRO_DROP1
02:28:18255MICRO_DROP1
02:28:20255MICRO_DROP1
02:28:46255MICRO_DROP2
02:28:51255MICRO_DROP1
02:29:01355SLOWDOWN12
02:29:03255MICRO_DROP1
02:29:05255MICRO_DROP2
02:29:08255MICRO_DROP1
02:29:10371MICRO_DROP1
02:29:22255MICRO_DROP1
02:29:28355MICRO_DROP1
02:29:28371MICRO_DROP1
02:29:47255MICRO_DROP1
02:29:53355MICRO_DROP1
02:30:02255MICRO_DROP2
02:30:22255MICRO_DROP1
02:30:54255SHORT_FAILURE3
02:31:01255MICRO_DROP1
02:31:05255MICRO_DROP1
02:31:14255MICRO_DROP2
02:31:18255MICRO_DROP1
02:31:59255MICRO_DROP1
02:32:14255MICRO_DROP1
02:32:34255MICRO_DROP1
02:32:34371MICRO_DROP1
02:32:41255MICRO_DROP1
02:32:49255MICRO_DROP1
02:33:09355MICRO_DROP1
02:33:35629SLOWDOWN37
02:33:51255MICRO_DROP1
02:34:11255MICRO_DROP1
02:34:54255MICRO_DROP1
02:35:00255MICRO_DROP1
02:35:02629SLOWDOWN10
02:35:25255MICRO_DROP1
02:35:25371MICRO_DROP1
02:35:29255MICRO_DROP1
02:35:35630MICRO_DROP1
02:35:46255MICRO_DROP1
02:36:02255MICRO_DROP2
02:36:25255MICRO_DROP1
02:36:27255MICRO_DROP1
02:36:30255MICRO_DROP1
02:36:38355MICRO_DROP1
02:36:46355MICRO_DROP1
02:36:49255MICRO_DROP1
02:37:07255MICRO_DROP1
02:37:14255SHORT_FAILURE3
02:37:30255SHORT_FAILURE3
02:37:35255SHORT_FAILURE4
02:37:59255MICRO_DROP1
02:37:59355MICRO_DROP1
02:38:04255MICRO_DROP1
02:38:37255MICRO_DROP1
02:38:53255MICRO_DROP1
02:39:04255MICRO_DROP1
02:39:31255MICRO_DROP1
02:39:40255MICRO_DROP1
02:40:03371MICRO_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.