Layer-2 loop contained in STO, row B
Network — transit & peering — STO · Out-of-band management — STO
Timeline
-
Resolved
Row B has been clean since 10:03 UTC. Duration: 9 minutes. Affected machines receive the SLA extension automatically.
-
Identified
A patching error during a machine replacement created a loop between two top-of-rack switches in row B. Storm control tripped on one side but not the other. The offending cable has been pulled.
-
Investigating
Machines in row B of STO are seeing severe packet loss since 09:54 UTC. The pattern looks like a broadcast storm. We are isolating the row.
A post-incident review is published here within five days of resolution.
Times are shown in your time zone ().
Related pages
- Service statusLive status of every gpuserver.io component and data centre, probed every 60 seconds from five cities, with 90-day uptime and the incident log since 2022.
- Incident historyEvery incident and maintenance window on gpuserver.io since monitoring began in September 2022, month by month, with its timeline and post-incident review.
- Service level agreementThe 99.9% commitment: what counts as downtime, how it is measured from outside, five minutes of term back per minute lost, and the exclusions in full.
- NetworkUnmetered ports up to 25 Gbit/s, two carriers and an IX per site, always-on DDoS filtering, routed IPv6 — and the four things we do not offer, stated up front.