Core switch line-card failure in ZRH, row C
Network — transit & peering — ZRH · Out-of-band management — ZRH
Timeline
-
Resolved
Every machine in row C has been reachable since 07:12 UTC. Duration of the outage: 50 minutes. The failed card is being replaced under an existing maintenance window; the replacement does not require another interruption. Affected machines receive the SLA extension automatically.
-
Monitoring
All 13 affected ports are up on the surviving card. We are checking each machine individually before closing this.
-
Identified
A line card in one of the two core switches in ZRH failed. Row C was dual-homed, but the failover on 13 ports did not complete because the standby links were still training. We are forcing those ports over to the surviving card.
-
Investigating
Machines in row C of ZRH lost network connectivity at 06:22 UTC. Rows outside C are unaffected. Engineers are on the floor.
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.