Internet quality by location

Measured period 2026-10-21 20:28 to 21:28 EDT · one measurement per second per location

At a glance

✓now  As of 21:13–21:27 EDT, ending 2 minutes ago, all 10 locations were clean.

630 clean729 clean76 cleanCONTROL clean125 clean212 clean255 clean355 clean371 clean629 clean

▲last 24h  2 location(s) went over the 1.0% threshold at some point in the last 24 hours: 629 (1h), 729 (1h). Worst single hour 1.57% at 629.

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
729127 minutes agooutside 0.079% - agrees within 1.0 point
125027 minutes agooutside 0.121% - agrees within 1.0 point
355034 minutes agooutside 0.067% - agrees within 1.0 point
371034 minutes agooutside 0.052% - agrees within 1.0 point
630027 minutes agono outside data
255054 minutes agooutside 0.043% - agrees within 1.0 point
629127 minutes agooutside 0.142% - agrees within 1.0 point
21204.7 hours agooutside 0.008% - agrees within 1.0 point
76074 minutes agooutside 0.0% - agrees within 1.0 point

One block per hour from 22: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 — 21:13–21:27 EDT

✓clean  As of 21:13–21:27 EDT, ending 2 minutes ago, all 10 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
630✓clean0.0%17.770/84115
729✓clean0.0%14.20/87615
76✓clean0.0%13.420/89415
CONTROL✓clean0.0%1.20/89915
125✓clean0.0%16.10/66413
212✓clean0.0%4.640/74613
255✓clean0.0%13.860/70714
355✓clean0.0%29.840/78914
371✓clean0.0%14.270/77014
629✓clean0.0%17.650/79515

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

▲watch  During 20:28–21:28 EDT on 2026-10-21, 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: 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 20:28–21:28 EDT on 2026-10-21

SeverityWhereWhat it means
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-21 15:28 to 2026-10-21 21:28 Eastern, across every measurement run in that window. 91.4% 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.

72913–18 ms · 9% of the window unmeasured
12514–33 ms · 9% of the window unmeasured
35513–36 ms · 9% of the window unmeasured
37113–18 ms · 9% of the window unmeasured
63016–39 ms · 9% of the window unmeasured
25513–17 ms · 9% of the window unmeasured
62915–43 ms · 9% of the window unmeasured
2124–6 ms · 9% of the window unmeasured
7612–17 ms · 9% of the window unmeasured

Each location during 20:28–21:28 EDT on 2026-10-21

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
729✓clean0.28%3.33%14.4321.4152.57
125✓clean0.23%2.67%15.8324.1596.89
355✓clean0.17%1.33%26.546.1975.33
371✓clean0.14%1.33%14.3319.8686.79
630✓clean0.14%1.67%18.1737.9661.76
255✓clean0.12%1.33%13.7919.4346.77
629✓clean0.08%1.0%17.4537.03109.58
212✓clean0.0%0.0%4.665.8816.21
76✓clean0.0%0.0%13.3117.2440.6

Every interruption during 20:28–21:28 EDT on 2026-10-21

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

TimeLocationKindSeconds
20:30:10355MICRO_DROP1
20:31:24255MICRO_DROP1
20:32:43255MICRO_DROP1
20:32:47371MICRO_DROP1
20:33:03355MICRO_DROP1
20:33:56255MICRO_DROP1
20:34:40371MICRO_DROP1
20:34:46355MICRO_DROP1
20:34:48355MICRO_DROP1
20:35:06371MICRO_DROP1
20:35:39255MICRO_DROP1
20:36:16355MICRO_DROP1
20:36:35371MICRO_DROP1
20:36:56355SLOWDOWN16
20:37:24355SLOWDOWN19
20:38:37629SLOWDOWN23
20:39:02629SLOWDOWN35
20:39:15355SLOWDOWN16
20:41:05355SLOWDOWN11
20:42:30355SLOWDOWN12
20:43:39630SLOWDOWN30
20:45:02125SLOWDOWN13
20:45:22355SLOWDOWN10
20:55:04371MICRO_DROP1
20:55:15355MICRO_DROP1
20:58:48629SLOWDOWN53
21:01:03630SLOWDOWN38
21:02:22125SHORT_FAILURE3
21:02:22729SHORT_FAILURE7
21:02:24630MICRO_DROP2
21:02:27125MICRO_DROP2
21:02:28629MICRO_DROP1
21:02:31729MICRO_DROP1
21:02:32125MICRO_DROP1
21:02:33729MICRO_DROP1
21:02:34125MICRO_DROP1
21:02:34630MICRO_DROP1
21:02:35729MICRO_DROP1
21:02:38629MICRO_DROP1
21:02:42630MICRO_DROP2
21:02:45125MICRO_DROP1
21:02:46629MICRO_DROP1
21:18:15125SLOWDOWN10
21:23:00630SLOWDOWN32
21:23:41630SLOWDOWN19

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.