Internet quality by location

Measured period 2026-10-07 03:30 to 04:30 EDT · one measurement per second per location

At a glance

▲now  As of 04:15–04:29 EDT, ending 2 minutes ago, 2 of 10 locations were over the 1.0% loss threshold: 255, 355.

255 watch355 watch371 clean629 clean630 clean729 clean125 clean212 clean76 cleanCONTROL clean

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

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
35552 minutes agooutside 1.086% - agrees within 1.0 point
255116 minutes agooutside 2.802%, higher than inside by 1.79 points - expected direction, the outside path is longer
37122 minutes agooutside 0.95% - agrees within 1.0 point
629116 minutes agooutside 0.062% - agrees within 1.0 point
630116 minutes agono outside data
729813 minutes agooutside 0.004% - agrees within 1.0 point
1251027 minutes agooutside 0.008% - agrees within 1.0 point
212019.2 hours agooutside 0.0% - agrees within 1.0 point
7607.4 hours agooutside 0.0% - agrees within 1.0 point

One block per hour from 05: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 — 04:15–04:29 EDT

▲degraded  As of 04:15–04:29 EDT, ending 2 minutes ago, 2 of 10 locations were over the 1.0% loss threshold: 255, 355.

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.45%14.2513/89915
355▲watch1.22%17.1511/89915
371✓clean0.89%14.428/90015
629✓clean0.56%16.995/89915
630✓clean0.22%17.682/89915
729✓clean0.11%13.851/89915
125✓clean0.0%15.830/89915
212✓clean0.0%4.720/90015
76✓clean0.0%12.740/89915
CONTROL✓clean0.0%1.210/89915

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

▲degraded  During 03:30–04:30 EDT on 2026-10-07, 2 of 9 locations lost more packets than the threshold allows: 355, 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 03:30–04:30 EDT on 2026-10-07

SeverityWhereWhat it means
MEDIUM255dropped more packets over the measured period than the threshold allows
MEDIUM355dropped 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 22:30 to 2026-10-07 04:30 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.

35515–20 ms · 0% of the window unmeasured
25513–30 ms · 0% of the window unmeasured
37113–20 ms · 0% of the window unmeasured
62914–41 ms · 0% of the window unmeasured
63015–35 ms · 0% of the window unmeasured
72913–18 ms · 0% of the window unmeasured
12513–23 ms · 0% of the window unmeasured
2124–5 ms · 0% of the window unmeasured
7611–17 ms · 0% of the window unmeasured

Each location during 03:30–04:30 EDT on 2026-10-07

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
355▲watch1.17%3.33%16.8230.7595.98
255▲watch1.01%3.33%14.0519.84141.14
371✓clean0.89%2.0%14.5821.6681.47
629✓clean0.17%1.0%16.5632.3777.33
630✓clean0.08%0.33%17.538.7778.38
729✓clean0.08%0.67%14.2320.9859.19
125✓clean0.03%0.33%15.7825.262.73
212✓clean0.0%0.0%4.635.9328.61
76✓clean0.0%0.0%12.615.5335.23

Every interruption during 03:30–04:30 EDT on 2026-10-07

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

TimeLocationKindSeconds
03:31:01355SLOWDOWN24
03:31:02371MICRO_DROP1
03:32:03355MICRO_DROP1
03:32:06371MICRO_DROP1
03:33:13355MICRO_DROP1
03:33:28255MICRO_DROP1
03:35:07125SLOWDOWN13
03:35:59355MICRO_DROP1
03:36:13255MICRO_DROP1
03:36:59371MICRO_DROP1
03:37:12371MICRO_DROP1
03:37:53355MICRO_DROP1
03:38:31255MICRO_DROP1
03:39:02371MICRO_DROP1
03:39:45729MICRO_DROP1
03:39:54729MICRO_DROP1
03:40:18629MICRO_DROP1
03:40:47371MICRO_DROP1
03:41:38371MICRO_DROP1
03:42:28630SLOWDOWN29
03:42:43255MICRO_DROP1
03:42:53355MICRO_DROP1
03:43:19355MICRO_DROP1
03:43:44355MICRO_DROP1
03:43:56355MICRO_DROP1
03:44:10255MICRO_DROP1
03:45:12355MICRO_DROP1
03:45:36371MICRO_DROP1
03:45:49255MICRO_DROP1
03:45:50355MICRO_DROP1
03:46:01255MICRO_DROP1
03:46:52355MICRO_DROP1
03:47:04255MICRO_DROP1
03:47:28355MICRO_DROP1
03:47:40355MICRO_DROP1
03:48:05255MICRO_DROP1
03:48:05355MICRO_DROP1
03:48:17355MICRO_DROP1
03:48:55355MICRO_DROP1
03:48:56371MICRO_DROP1
03:49:07355MICRO_DROP1
03:50:37371MICRO_DROP1
03:52:09371MICRO_DROP1
03:52:59371MICRO_DROP1
03:53:24371MICRO_DROP1
03:53:24630MICRO_DROP1
03:53:26255MICRO_DROP1
03:53:52255MICRO_DROP1
03:54:17255MICRO_DROP1
03:54:19371MICRO_DROP1
03:55:39371MICRO_DROP1
03:56:22255MICRO_DROP1
03:56:22355MICRO_DROP1
03:56:56371MICRO_DROP1
03:57:25355MICRO_DROP1
03:57:38355MICRO_DROP1
03:58:20629SLOWDOWN24
03:58:27255MICRO_DROP1
04:00:09355MICRO_DROP1
04:01:12355MICRO_DROP1
04:01:46371MICRO_DROP1
04:02:16355MICRO_DROP1
04:02:29125SLOWDOWN19
04:02:53355MICRO_DROP1
04:03:01371MICRO_DROP1
04:03:30255MICRO_DROP1
04:03:30355MICRO_DROP1
04:03:39371MICRO_DROP1
04:03:55255MICRO_DROP1
04:04:35125MICRO_DROP1
04:04:35255MICRO_DROP1
04:05:13255MICRO_DROP1
04:05:39355MICRO_DROP1
04:06:14255MICRO_DROP1
04:07:04255MICRO_DROP1
04:07:57371MICRO_DROP1
04:08:09371MICRO_DROP1
04:08:35355MICRO_DROP1
04:08:45630SLOWDOWN55
04:08:55255MICRO_DROP1
04:09:00355MICRO_DROP1
04:09:12355MICRO_DROP1
04:09:45255MICRO_DROP1
04:10:16355MICRO_DROP1
04:10:18371MICRO_DROP1
04:11:34371MICRO_DROP1
04:11:40255MICRO_DROP1
04:12:56125SLOWDOWN15
04:14:01355MICRO_DROP1
04:15:02255MICRO_DROP1
04:15:50371MICRO_DROP1
04:16:15255MICRO_DROP1
04:17:39355MICRO_DROP1
04:17:45371MICRO_DROP1
04:17:55629MICRO_DROP1
04:18:21355MICRO_DROP1
04:18:26729MICRO_DROP1
04:18:27629MICRO_DROP1
04:18:33255MICRO_DROP1
04:18:34630MICRO_DROP1
04:18:36629MICRO_DROP1
04:19:24355MICRO_DROP1
04:19:53371MICRO_DROP1
04:20:20355MICRO_DROP1
04:20:30371MICRO_DROP1
04:20:33355MICRO_DROP1
04:20:40255MICRO_DROP1
04:21:04255MICRO_DROP1
04:21:07255MICRO_DROP1
04:21:30255MICRO_DROP1
04:21:54255MICRO_DROP1
04:22:13355MICRO_DROP1
04:22:19255MICRO_DROP1
04:22:25371MICRO_DROP1
04:23:03255MICRO_DROP1
04:24:11255MICRO_DROP1
04:24:36255MICRO_DROP1
04:25:04255MICRO_DROP1
04:25:11355MICRO_DROP1
04:25:51630MICRO_DROP1
04:25:52629MICRO_DROP1
04:25:56629MICRO_DROP1
04:26:40355MICRO_DROP1
04:26:42371MICRO_DROP1
04:26:52355MICRO_DROP1
04:27:17371MICRO_DROP1
04:27:44355MICRO_DROP1
04:28:17629SLOWDOWN82
04:28:38630SLOWDOWN45
04:29:15355MICRO_DROP1
04:29:28371MICRO_DROP1
04:30:07371MICRO_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.