Internet quality by location

Measured period 2026-10-21 06:33 to 07:33 EDT · one measurement per second per location

At a glance

▲now  As of 07:18–07:32 EDT, ending 2 minutes ago, 4 of 10 locations were over the 1.0% loss threshold: 629, 729, 125, 630.

629 degraded729 watch125 watch630 watch371 clean212 clean255 clean355 clean76 cleanCONTROL clean

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

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
62916 minutes agooutside 0.159%, LOWER than inside by 1.00 points - the loss may be at or near our own measurement, not the line
72914 minutes agooutside 0.118% - agrees within 1.0 point
12518 minutes agooutside 0.172% - agrees within 1.0 point
63016 minutes agono outside data
37105 minutes agooutside 0.051% - agrees within 1.0 point
355032 minutes agooutside 0.054% - agrees within 1.0 point
212021 minutes agooutside 0.0% - agrees within 1.0 point
255079 minutes agooutside 0.064% - agrees within 1.0 point
7605.5 hours agooutside 0.0% - agrees within 1.0 point

One block per hour from 08: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 — 07:18–07:32 EDT

▲degraded  As of 07:18–07:32 EDT, ending 2 minutes ago, 4 of 10 locations were over the 1.0% loss threshold: 629, 729, 125, 630.

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
629▲degraded5.33%16.8140/75115
729▲watch4.4%14.5738/86415
125▲watch3.08%15.8220/64913
630▲watch3.03%18.6425/82615
371✓clean0.25%13.752/79514
212✓clean0.0%4.830/72813
255✓clean0.0%13.460/68114
355✓clean0.0%13.780/75514
76✓clean0.0%13.350/89615
CONTROL✓clean0.0%1.220/89915

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

▲degraded  During 06:33–07:33 EDT on 2026-10-21, 2 of 9 locations lost more packets than the threshold allows: 629, 729.

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 06:33–07:33 EDT on 2026-10-21

SeverityWhereWhat it means
MEDIUM629dropped more packets over the measured period than the threshold allows
MEDIUM729dropped more packets over the measured period than the threshold allows
MEDIUM125loss was concentrated in one five-minute stretch
MEDIUM629loss was concentrated in one five-minute stretch
MEDIUM630loss was concentrated in one five-minute stretch
MEDIUM729loss 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-21 01:33 to 2026-10-21 07:33 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.

62915–41 ms · 0% of the window unmeasured
72914–18 ms · 0% of the window unmeasured
12514–36 ms · 1% of the window unmeasured
63016–35 ms · 0% of the window unmeasured
37113–17 ms · 0% of the window unmeasured
35513–37 ms · 0% of the window unmeasured
2124–5 ms · 1% of the window unmeasured
25513–16 ms · 0% of the window unmeasured
7612–17 ms · 0% of the window unmeasured

Each location during 06:33–07:33 EDT on 2026-10-21

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
629▲watch1.16%11.67%17.2932.6389.15
729▲watch1.06%12.33%14.1821.2957.85
125✓clean0.7%7.33%15.7624.1476.83
630✓clean0.7%8.0%18.3239.669.14
371✓clean0.26%1.33%14.0519.8104.5
355✓clean0.09%0.33%13.820.6586.73
212✓clean0.03%0.33%4.715.8811.12
255✓clean0.03%0.33%13.5617.4139.38
76✓clean0.0%0.0%13.2617.236.62

Every interruption during 06:33–07:33 EDT on 2026-10-21

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

TimeLocationKindSeconds
06:35:02125SLOWDOWN10
06:35:37355MICRO_DROP1
06:36:51255MICRO_DROP1
06:52:45630SLOWDOWN17
06:52:53371MICRO_DROP1
06:53:46355MICRO_DROP1
07:02:17355MICRO_DROP1
07:03:53125MICRO_DROP1
07:07:35371MICRO_DROP1
07:09:35371MICRO_DROP1
07:10:17371MICRO_DROP1
07:11:12371MICRO_DROP1
07:12:09355SLOWDOWN10
07:12:59212MICRO_DROP1
07:16:57371MICRO_DROP1
07:17:23371MICRO_DROP1
07:19:45729MICRO_DROP1
07:20:09629MICRO_DROP1
07:20:10125MICRO_DROP1
07:20:11729SHORT_FAILURE3
07:20:13125MICRO_DROP1
07:20:17125MICRO_DROP1
07:20:17629MICRO_DROP1
07:20:17729MICRO_DROP1
07:20:20729MICRO_DROP1
07:20:24629SHORT_FAILURE3
07:20:30371MICRO_DROP1
07:20:31125MICRO_DROP1
07:20:32629MICRO_DROP1
07:20:44630MICRO_DROP1
07:20:45729MICRO_DROP1
07:22:15125MICRO_DROP1
07:22:15629MICRO_DROP1
07:23:28125MICRO_DROP1
07:23:28629SHORT_FAILURE3
07:23:29630MICRO_DROP1
07:23:32630MICRO_DROP2
07:23:32729MICRO_DROP1
07:23:33629MICRO_DROP1
07:23:35630MICRO_DROP1
07:23:37630SLOWDOWN21
07:23:39125MICRO_DROP1
07:23:40729MICRO_DROP1
07:23:44629MICRO_DROP1
07:23:44630MICRO_DROP1
07:23:46125MICRO_DROP1
07:23:46729SHORT_FAILURE4
07:23:47629SHORT_FAILURE5
07:23:47630MICRO_DROP1
07:23:48125MICRO_DROP2
07:23:49729SLOWDOWN14
07:23:51125MICRO_DROP2
07:23:51630SHORT_FAILURE3
07:23:51729MICRO_DROP1
07:23:52629SLOWDOWN24
07:23:54729SHORT_FAILURE15
07:23:56125MICRO_DROP2
07:23:56629MICRO_DROP1
07:23:56630MICRO_DROP1
07:23:58629MICRO_DROP2
07:23:58630MICRO_DROP2
07:24:01125MICRO_DROP1
07:24:01629MICRO_DROP1
07:24:02630MICRO_DROP1
07:24:03629SHORT_FAILURE3
07:24:03630SLOWDOWN23
07:24:06630MICRO_DROP1
07:24:07125MICRO_DROP2
07:24:07629MICRO_DROP1
07:24:09629MICRO_DROP1
07:24:09729SLOWDOWN15
07:24:10125MICRO_DROP1
07:24:10729SHORT_FAILURE4
07:24:11630SHORT_FAILURE4
07:24:12629MICRO_DROP2
07:24:13125MICRO_DROP1
07:24:16729MICRO_DROP1
07:24:17629SHORT_FAILURE6
07:24:17630MICRO_DROP1
07:24:18125MICRO_DROP2
07:24:21630SHORT_FAILURE4
07:24:21729SHORT_FAILURE3
07:24:23125MICRO_DROP1
07:24:25629MICRO_DROP1
07:26:35125MICRO_DROP1
07:26:35629MICRO_DROP1
07:26:37629MICRO_DROP1
07:28:07630MICRO_DROP1
07:28:09629MICRO_DROP1
07:28:11629MICRO_DROP1
07:28:14629MICRO_DROP2
07:29:01371MICRO_DROP1
07:30:45729MICRO_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.