Measured period 2026-10-03 17:31 to 18:25 EDT · one measurement per second per location
✓clean As of 18:09–18:23 EDT, ending 2 minutes ago, all 9 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.
| Location | State | Loss | Typical ms | Lost / sent | Minutes of data |
|---|---|---|---|---|---|
| 76 | ✓clean | 0.22% | 12.75 | 2/900 | 15 |
| 355 | ✓clean | 0.0% | 13.97 | 0/900 | 15 |
| 255 | ✓clean | 0.0% | 14.5 | 0/900 | 15 |
| 212 | ✓clean | 0.0% | 4.73 | 0/900 | 15 |
| 629 | ✓clean | 0.0% | 19.87 | 0/900 | 15 |
| 630 | ✓clean | 0.0% | 18.15 | 0/900 | 15 |
| 371 | ✓clean | 0.0% | 13.48 | 0/900 | 15 |
| 125 | ✓clean | 0.0% | 15.38 | 0/900 | 15 |
| 729 | ✓clean | 0.0% | 13.56 | 0/900 | 15 |
A measurement runs automatically every hour and republishes this page. Page built 18:25 EDT. Newest measured minute on record: 18:23 EDT, 2 minutes ago. The measurement period summarised below ended 18:25 EDT, less than a minute ago. This page reloads itself every 10 minutes.
▲watch During 17:31–18:25 EDT on 2026-10-03, 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: 3217 seconds, one sample per second per location. A single lost second moves a location's loss figure by 0.031 percentage points, so small percentages rest on few events. Graphs below cover a longer window and are labelled separately.
| Severity | Where | What it means |
|---|---|---|
| MEDIUM | 255 | loss was concentrated in one five-minute stretch |
| INFO | independent reference | the independent reference also lost packets, so some loss belongs to the wider internet |
| INFO | 125 | not enough history yet to compare this location against its own normal |
| INFO | 212 | not enough history yet to compare this location against its own normal |
| INFO | 255 | not enough history yet to compare this location against its own normal |
| INFO | 355 | not enough history yet to compare this location against its own normal |
| INFO | 371 | not enough history yet to compare this location against its own normal |
| INFO | 629 | not enough history yet to compare this location against its own normal |
| INFO | 630 | not enough history yet to compare this location against its own normal |
| INFO | 729 | not enough history yet to compare this location against its own normal |
| INFO | 76 | not enough history yet to compare this location against its own normal |
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 72 hours, 2026-09-30 18:25 to 2026-10-03 18:25 Eastern, across every measurement run in that window. 8.0% of those hours carry data, because measurement runs in discrete sessions rather than continuously. An unmeasured period is not a quiet period.
| Location | State | Loss | Worst 5 min | Typical ms | Slowest 1 in 20 | Worst ms |
|---|---|---|---|---|---|---|
| 255 | ✓clean | 0.93% | 10.0% | 14.64 | 20.43 | 56.09 |
| 355 | ✓clean | 0.12% | 0.67% | 14.14 | 21.92 | 58.2 |
| 76 | ✓clean | 0.12% | 0.33% | 12.66 | 16.43 | 65.63 |
| 125 | ✓clean | 0.0% | 0.0% | 15.41 | 24.1 | 47.68 |
| 212 | ✓clean | 0.0% | 0.0% | 4.68 | 5.92 | 18.23 |
| 371 | ✓clean | 0.0% | 0.0% | 13.77 | 19.23 | 131.59 |
| 629 | ✓clean | 0.0% | 0.0% | 16.8 | 40.27 | 58.9 |
| 630 | ✓clean | 0.0% | 0.0% | 17.77 | 39.98 | 57.29 |
| 729 | ✓clean | 0.0% | 0.0% | 13.82 | 19.27 | 35.26 |
Includes one-second blips, which are harmless alone but indicate an unsteady connection. Times are Eastern.
| Time | Location | Kind | Seconds |
|---|---|---|---|
| 17:35:03 | 355 | MICRO_DROP | 1 |
| 17:38:13 | 76 | MICRO_DROP | 1 |
| 17:38:40 | 355 | SLOWDOWN | 11 |
| 17:40:47 | 355 | SLOWDOWN | 21 |
| 17:40:49 | 355 | MICRO_DROP | 1 |
| 17:43:19 | 355 | MICRO_DROP | 1 |
| 17:45:11 | 76 | MICRO_DROP | 1 |
| 17:46:55 | 355 | MICRO_DROP | 1 |
| 17:46:57 | 355 | SLOWDOWN | 11 |
| 17:49:47 | 355 | SLOWDOWN | 16 |
| 17:54:56 | 629 | SLOWDOWN | 20 |
| 17:55:51 | 629 | SLOWDOWN | 39 |
| 17:56:36 | 629 | SLOWDOWN | 14 |
| 17:57:02 | 629 | SLOWDOWN | 13 |
| 17:57:46 | 255 | MICRO_DROP | 1 |
| 17:57:53 | 255 | SHORT_FAILURE | 3 |
| 17:58:00 | 255 | MICRO_DROP | 1 |
| 17:58:51 | 255 | MICRO_DROP | 1 |
| 17:58:58 | 255 | MICRO_DROP | 1 |
| 17:59:30 | 255 | SHORT_FAILURE | 3 |
| 17:59:44 | 255 | MICRO_DROP | 1 |
| 17:59:53 | 255 | MICRO_DROP | 2 |
| 18:00:03 | 255 | MICRO_DROP | 1 |
| 18:00:05 | 255 | MICRO_DROP | 1 |
| 18:00:15 | 255 | MICRO_DROP | 1 |
| 18:00:17 | 255 | MICRO_DROP | 2 |
| 18:00:44 | 255 | MICRO_DROP | 2 |
| 18:00:53 | 255 | MICRO_DROP | 2 |
| 18:01:00 | 255 | MICRO_DROP | 1 |
| 18:01:13 | 255 | MICRO_DROP | 2 |
| 18:01:43 | 255 | MICRO_DROP | 1 |
| 18:01:53 | 255 | MICRO_DROP | 1 |
| 18:02:02 | 255 | MICRO_DROP | 2 |
| 18:02:12 | 255 | MICRO_DROP | 1 |
| 18:05:08 | 630 | SLOWDOWN | 29 |
| 18:09:58 | 76 | MICRO_DROP | 1 |
| 18:17:13 | 76 | MICRO_DROP | 1 |
| 18:22:38 | 629 | SLOWDOWN | 20 |
| 18:23:11 | 629 | SLOWDOWN | 18 |
| 18:23:25 | 630 | SLOWDOWN | 14 |
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; zero is normal. Typical ms is the middle response time. Slowest 1 in 20 is the 95th percentile. MICRO_DROP is one or two lost seconds, SHORT_FAILURE three to twenty-nine, OUTAGE thirty or more, and SLOWDOWN at least ten seconds much slower than that location's own normal.