Top-of-rack switch firmware, rows A–B — ZRH
Network — transit & peering — ZRH
What is planned
The top-of-rack switches in rows A to B of ZRH receive a firmware update. Each switch reloads once, which interrupts the network for the machines in its rack for about 90 seconds. Racks are done one at a time. Running workloads are not affected, only reachability during the reload. The interruption is counted against the SLA of the affected machines even though it is announced.
Timeline
-
Completed
All switches in rows A–B of ZRH are on the new firmware. Each rack was interrupted once, for under two minutes.
-
In progress
We need about 16 more minutes than announced. The work is proceeding normally; the window is extended by that amount.
-
In progress
Maintenance has started with row A. Each rack will see about 90 seconds of interruption when its switch reloads.
-
Scheduled
The top-of-rack switches in rows A to B of ZRH receive a firmware update. Each switch reloads once, which interrupts the network for the machines in its rack for about 90 seconds. Racks are done one at a time. Running workloads are not affected, only reachability during the reload. The interruption is counted against the SLA of the affected machines even though it is announced.
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.