This incident has been resolved - the affected switch will continue to be monitored and will be replaced during our usual maintenance window.
Posted 3 months ago. Apr 04, 2019 - 11:17 AEDT
We will continue to monitor the affected switch for the time being in case its replacement becomes more urgent.
Posted 3 months ago. Apr 04, 2019 - 08:30 AEDT
A failed hardware component in the affected switch has been identified as the cause of the crash. This component is not critical for normal switch operation, but caused a management process to crash and the switch to cease forwarding traffic. Mastership of the affected top-of-rack switching cluster has been transferred to a fully healthy member, and a replacement of the affected switch will be performed during a scheduled future outage window.
Posted 3 months ago. Apr 04, 2019 - 08:23 AEDT
A crashed top-of-rack switching device has been identified as the cause of the outage. The device has been rebooted and service has been restored. We are currently looking further into the cause of the crash.
Posted 3 months ago. Apr 04, 2019 - 08:13 AEDT
We are currently investigating an outage affecting multiple VPS hypervisor nodes. Affected nodes are: