Pulse · network telemetry
The network, in the open.
Live status, regional latency, and an indicative speed test. Incidents are logged honestly — including the ones that touched nobody.
All systems nominal
updated 2026-10-24 22:08ZRegional latency
Speed test
indicative—msround-trip
—Mbpsdownload
Measures real round-trips from your browser to a Segal endpoint. Results are indicative — affected by your local link, device, and route, not a certified line rate.
Per-region
| Region | Code | Latency | Packet loss |
|---|---|---|---|
| Austin | AUS | 3 ms | 0.007% |
| Denver | DEN | 6.2 ms | 0.020% |
| Raleigh | RDU | 3 ms | 0.014% |
| Portland | PDX | 6.2 ms | 0.000% |
| Nashville | BNA | 5 ms | 0.000% |
| London | LHR | 13.2 ms | 0.000% |
| Frankfurt | FRA | 12.1 ms | 0.002% |
| Singapore | SIN | 20.1 ms | 0.018% |
| Tokyo | NRT | 16.1 ms | 0.017% |
| São Paulo | GRU | 24.1 ms | 0.001% |
| Sydney | SYD | 24.1 ms | 0.000% |
| Johannesburg | JNB | 30.1 ms | 0.000% |
Incident history
- SEV3INC-2026-04182026-04-18 02:14Z → 2026-04-18 02:41ZStrand
Single-fiber cut on the Denver–Salt Lake long-haul. Lattice rerouted affected prefixes; no customer-visible loss. Splice restored in 27 min.
- SEV2INC-2026-03022026-03-02 19:05Z → 2026-03-02 19:52ZStrand
Peering congestion at the Raleigh IX during a transit partner maintenance. Elevated latency (peak 11 ms) for ~47 min. Traffic shifted to alternate peers.
- SEV3INC-2026-01192026-01-19 08:30Z → ongoingHalo
Pre-production Halo relay node degraded during cold-weather trial. No customer traffic carried (Halo is in development). Tracking as an open engineering item.