Internet quality by location

Measured period 2026-10-19 02:33 to 03:33 EDT · one measurement per second per location

At a glance

▲now  As of 03:18–03:32 EDT, ending 1 minute ago, 1 of 10 locations were over the 1.0% loss threshold: 629.

629 watch630 clean125 clean355 clean371 clean729 clean212 clean255 clean76 cleanCONTROL clean

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

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
62917 minutes agooutside 0.273% - agrees within 1.0 point
63017 minutes agono outside data
125111 minutes agooutside 0.191% - agrees within 1.0 point
729011 minutes agooutside 0.18% - agrees within 1.0 point
355014 minutes agooutside 0.023% - agrees within 1.0 point
37107 minutes agooutside 0.029% - agrees within 1.0 point
21206.7 hours agooutside 0.0% - agrees within 1.0 point
255276 minutes agooutside 0.012% - agrees within 1.0 point
7605.8 hours agooutside 0.0% - agrees within 1.0 point

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

▲degraded  As of 03:18–03:32 EDT, ending 1 minute ago, 1 of 10 locations were over the 1.0% loss threshold: 629.

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▲watch1.13%16.749/79415
630✓clean0.36%17.483/84315
125✓clean0.15%16.651/64813
355✓clean0.13%32.031/74714
371✓clean0.13%13.961/78414
729✓clean0.12%14.081/86515
212✓clean0.0%4.540/72113
255✓clean0.0%13.430/73214
76✓clean0.0%13.110/89015
CONTROL✓clean0.0%1.210/90015

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

▲degraded  During 02:33–03:33 EDT on 2026-10-19, 1 of 9 locations lost more packets than the threshold allows: 629.

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 02:33–03:33 EDT on 2026-10-19

SeverityWhereWhat it means
MEDIUM629dropped 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-18 21:33 to 2026-10-19 03: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.

62914–45 ms
63016–42 ms
12514–37 ms · 1% of the window unmeasured
72913–18 ms
35513–36 ms · 0% of the window unmeasured
37113–17 ms · 0% of the window unmeasured
2124–5 ms · 1% of the window unmeasured
25513–21 ms · 0% of the window unmeasured
7612–16 ms

Each location during 02:33–03:33 EDT on 2026-10-19

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
629▲watch1.13%10.33%18.0837.32109.78
630✓clean0.95%10.33%18.6938.16169.79
125✓clean0.64%7.0%16.0524.6457.98
729✓clean0.5%5.33%14.2521.4667.43
355✓clean0.06%0.33%30.7444.94100.8
371✓clean0.03%0.33%13.9818.793.3
212✓clean0.0%0.0%4.665.8632.61
255✓clean0.0%0.0%13.4118.7827.09
76✓clean0.0%0.0%13.1116.2836.74

Every interruption during 02:33–03:33 EDT on 2026-10-19

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

TimeLocationKindSeconds
02:33:44355MICRO_DROP1
02:54:58125SLOWDOWN18
02:55:41729MICRO_DROP1
02:59:19630SLOWDOWN17
02:59:37629SLOWDOWN10
03:00:03629SLOWDOWN15
03:09:38125MICRO_DROP1
03:09:42629SHORT_FAILURE3
03:09:44630SHORT_FAILURE3
03:09:45729SHORT_FAILURE8
03:09:47629MICRO_DROP2
03:09:48125MICRO_DROP1
03:09:48630MICRO_DROP1
03:09:50125SHORT_FAILURE4
03:09:50629MICRO_DROP2
03:09:50630SHORT_FAILURE3
03:09:53629SHORT_FAILURE7
03:09:53729SLOWDOWN15
03:09:54630SHORT_FAILURE7
03:09:54729MICRO_DROP1
03:09:55125SHORT_FAILURE3
03:09:56729MICRO_DROP2
03:10:00125SHORT_FAILURE3
03:10:01629SHORT_FAILURE4
03:10:02629SLOWDOWN12
03:10:02729MICRO_DROP1
03:10:03630MICRO_DROP2
03:10:07630SHORT_FAILURE3
03:10:08629MICRO_DROP2
03:10:12629MICRO_DROP1
03:10:33629MICRO_DROP2
03:10:34630MICRO_DROP1
03:10:35125MICRO_DROP2
03:10:37629MICRO_DROP1
03:10:39629SLOWDOWN12
03:10:40125MICRO_DROP2
03:10:45629MICRO_DROP1
03:10:46630MICRO_DROP1
03:10:48125MICRO_DROP1
03:10:50125MICRO_DROP1
03:10:51630MICRO_DROP2
03:10:52729MICRO_DROP1
03:10:58125MICRO_DROP1
03:11:02125MICRO_DROP1
03:11:02629MICRO_DROP1
03:11:02630MICRO_DROP1
03:11:02729MICRO_DROP1
03:11:07629MICRO_DROP2
03:11:07630MICRO_DROP1
03:11:10125MICRO_DROP1
03:11:10630MICRO_DROP1
03:11:14629MICRO_DROP1
03:11:14630MICRO_DROP1
03:11:29630MICRO_DROP1
03:11:32630MICRO_DROP2
03:11:33729MICRO_DROP2
03:11:38629MICRO_DROP1
03:11:42630MICRO_DROP1
03:11:58629MICRO_DROP1
03:18:29630SLOWDOWN66
03:19:34355MICRO_DROP1
03:21:58125MICRO_DROP1
03:22:00729MICRO_DROP1
03:24:13629MICRO_DROP1
03:25:54629MICRO_DROP1
03:25:59629MICRO_DROP1
03:26:03630MICRO_DROP1
03:26:06371MICRO_DROP1
03:26:07629MICRO_DROP2
03:26:11629SHORT_FAILURE3
03:26:17630MICRO_DROP1
03:26:22629MICRO_DROP1
03:26:25630MICRO_DROP1
03:31:04629SLOWDOWN18
03:31:29629SLOWDOWN22

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.