Servers Australia Outage History

Servers Australia is up right now

Servers Australia had 27 outages in the last 2 years totaling 41h 57m of downtime — averaging 1.1 incidents per month.

There were 27 Servers Australia outages since May 17, 2025 totaling 41h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mysau.com.au

Notice May 21, 2025

SolusVM - Degraded Node

Detected by Pingoru
May 21, 2025, 11:20 PM UTC
Resolved
May 22, 2025, 05:30 AM UTC
Duration
6h 10m
Affected: SydneyCloud Servers
Timeline · 3 updates
  1. monitoring May 21, 2025, 11:20 PM UTC

    A node hosting SolusVM Cloud Servers went offline temporarily. This has been brought back online, and all affected VMs have powered back on. We're looking into ways to prevent this in future. This incident did NOT impact Cloud Servers hosted on our VMware platform.

  2. monitoring May 21, 2025, 11:25 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved May 22, 2025, 05:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 17, 2025

Switch problem - Equinix SY1

Detected by Pingoru
May 17, 2025, 10:41 AM UTC
Resolved
May 18, 2025, 10:28 PM UTC
Duration
1d 11h
Affected: Equinix SY1SydneyNetwork
Timeline · 3 updates
  1. investigating May 17, 2025, 10:41 AM UTC

    Engineers have been alerted to an issue with a switching/routing device in the Equinix SY1 facility. We are currently investigating the situation and will provide further updates as available.

  2. monitoring May 17, 2025, 11:06 AM UTC

    Engineers have identified the issue with the core switching stack in SY1. At 20:19 the core switch stack had a failed switch member, the stack failed over to a redundant stack member within about 90 seconds. We can confirm that the failed switch has now been rebooted and has recovered back into the stack. All customer workloads should have returned to normal. Our Network engineers will be monitoring the core to ensure stability before closing this status.

  3. resolved May 18, 2025, 10:28 PM UTC

    This incident has been resolved.

Read the full incident report →