Core router software upgrade — ZRH
Network — transit & peering — ZRH
What is planned
We will upgrade the operating system on the two core routers in ZRH, one after the other. Each router is drained before it reloads, so traffic stays on the other one. Expect up to 60 seconds of reduced redundancy per router while its BGP sessions reconverge; no machine should lose connectivity. Out-of-band access is unaffected.
Timeline
-
Completed
Both core routers in ZRH are on the new release and carrying traffic. No connectivity was lost during the window.
-
In progress
We need about 19 more minutes than announced. The work is proceeding normally; the window is extended by that amount.
-
In progress
Maintenance has started. The first core router in ZRH has been drained and is reloading.
-
Scheduled
We will upgrade the operating system on the two core routers in ZRH, one after the other. Each router is drained before it reloads, so traffic stays on the other one. Expect up to 60 seconds of reduced redundancy per router while its BGP sessions reconverge; no machine should lose connectivity. Out-of-band access is unaffected.
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.