Servers Australia Outage History

Servers Australia is up right now

There were 5 Servers Australia outages since February 4, 2026 totaling 93h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Notice April 16, 2026

Syncom SYD2 - Rack power disturbance

Detected by Pingoru
Apr 16, 2026, 02:30 PM UTC
Resolved
Apr 17, 2026, 01:59 AM UTC
Duration
11h 29m
Affected: SydneyDedicated ServersSYD2
Timeline · 4 updates
  1. investigating Apr 16, 2026, 02:30 PM UTC

    Engineers have identified a power issue affecting a single rack in the Syncom SYD2 facility. A technician has been dispatched to the site and will provide an update once the problem has been assessed. If you have any questions or are experiencing any interruption to services and would like to enquire further, please raise a case via the MySAU portal.

  2. identified Apr 16, 2026, 02:54 PM UTC

    Technicians have identified an issue with a power supply in this rack which caused circuit breaker trip. The problem server(s) have been disconnected and power has been restored to the rack, and services in this rack should now be coming back online. We will monitor the situation and provide an update once we have confirmed everything is stable.

  3. monitoring Apr 16, 2026, 03:21 PM UTC

    Technicians have replaced any failed power supplies and have confirmed the rack remains stable. The situation will be monitored for any changes.

  4. resolved Apr 17, 2026, 01:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 14, 2026

Network Failure - Equinix SY4

Detected by Pingoru
Apr 14, 2026, 04:50 AM UTC
Resolved
Apr 15, 2026, 05:20 AM UTC
Duration
1d
Affected: SydneyNetworkEquinix SY4Dedicated Servers
Timeline · 4 updates
  1. identified Apr 14, 2026, 04:50 AM UTC

    Network engineers are aware of a network issue affecting a single top-of-rack switch in the Equinix SY4 data centre, which is impacting some dedicated servers. We are arranging onsite hands to assist further. No restoration time is available at this stage. We will provide further updates as soon as possible.

  2. identified Apr 14, 2026, 05:14 AM UTC

    The technician is onsite with replacement hardware. We expect an update within the next 10 minutes.

  3. monitoring Apr 14, 2026, 05:25 AM UTC

    The technician has successfully replaced the failed hardware, and connectivity has been restored. Please contact our support team should you still be experiencing issues with your service.

  4. resolved Apr 15, 2026, 05:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026

Fortigate Firewall - Reduced Network Capacity

Detected by Pingoru
Mar 12, 2026, 09:15 PM UTC
Resolved
Mar 14, 2026, 01:36 AM UTC
Duration
1d 4h
Affected: Firewall
Timeline · 8 updates
  1. investigating Mar 12, 2026, 09:15 PM UTC

    We have had a number of customers advise that they are experiencing network capacity constraints when routing through our Sydney FortiGate Firewall Cluster. We have identified that there is an issue with the device memory and that throughput is constrained. Our Network Operations team has been engaged and they are working with FortiNet support to find the root cause of the issue. Updates to Follow

  2. identified Mar 12, 2026, 10:11 PM UTC

    The vendor has identified a possible firmware issue. The Fortinet team is currently working with us to implement a workaround while the root cause is investigated further.

  3. identified Mar 12, 2026, 10:24 PM UTC

    To implement the workaround on the Primary Device, we need to failover workloads to the redundant side of this Firewall Cluster. This process should not impact workloads further, but we are issuing a cautionary advisory that there may be a brief disruption when this happens. Once the workaround is put in place, the cluster will be restored to full synchronous HA configuration

  4. identified Mar 12, 2026, 10:42 PM UTC

    Firewall switchover has occurred, and the former standby unit is now the primary. Engineers will perform some further diagnostics and then reboot the standby unit to clear the error condition. Further updates will be provided as available.

  5. monitoring Mar 12, 2026, 11:11 PM UTC

    Per recommendation from the vendor, we will leave the HA cluster un the current state and monitor the situation further. Services should be operating as normal, and no further switchovers are required. The vendor has confirmed that the issue is resolved in a firmware release that is scheduled for late April. Engineers will monitor the status of the cluster until the firmware update is available, and pre-emptively perform a switchover should the cluster approach the memory consumption threshold recommended by the vendor. If you have any questions or continue to experience issues, please raise a case via the MySAU portal.

  6. monitoring Mar 13, 2026, 12:18 AM UTC

    We are currently in the process of promoting the SY3 Firewall HA member back to primary after changes made by our Network Operations Team and the vendor earlier this morning. No customer impact is expected.

  7. monitoring Mar 13, 2026, 12:30 AM UTC

    This failover is now complete. Please update or raise a case in the MySAU portal if you are experiencing any further issues.

  8. resolved Mar 14, 2026, 01:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 6, 2026

Loss of Power - Rack F13 - SYD2 Colocation

Detected by Pingoru
Feb 06, 2026, 02:46 AM UTC
Resolved
Feb 06, 2026, 03:32 AM UTC
Duration
45m
Affected: SYD2
Timeline · 2 updates
  1. identified Feb 06, 2026, 02:46 AM UTC

    There was a brief power disruption affecting rack F13 in the SYD2 data centre. Services are currently being restored and are coming back online following the interruption. If you have any services that remain impacted or require assistance, please raise a case via the MySAU.com.au portal and our Support Team will be happy to assist.

  2. resolved Feb 06, 2026, 03:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 4, 2026

Sydney FortiGate Firewall

Detected by Pingoru
Feb 04, 2026, 07:17 PM UTC
Resolved
Feb 05, 2026, 11:25 PM UTC
Duration
1d 4h
Affected: SydneyCloud ServersFirewall
Timeline · 8 updates
  1. investigating Feb 04, 2026, 07:17 PM UTC

    We have identified an issue affecting customers with IPsec tunnels terminating on the Sydney FortiGate Firewall cluster. Following scheduled maintenance performed earlier this morning (https://status.mysau.com.au/incidents/5zddznmjtl8h) some IPsec tunnels are currently offline and are not re-establishing as expected. Our network and engineering teams are actively investigating this issue and are working directly with Fortinet Support to restore affected services as quickly as possible. At this time, only customers with IPsec tunnels in Sydney are impacted. Other services remain operational. Further updates will be provided as more information becomes available.

  2. identified Feb 04, 2026, 08:19 PM UTC

    Our network and engineering teams have identified a number of configuration inconsistencies following the firmware update performed earlier this morning. We are currently preparing to roll back the firmware update and restore the firewall configuration from backup in order to return service stability and consistency. This rollback will cause a service outage of up to 10 minutes while the configuration is reloaded. The rollback is scheduled to start between 7:30 AM and 08:00 AM Further updates will be provided as work progresses.

  3. identified Feb 04, 2026, 08:56 PM UTC

    We are currently working with FortiGate support to reload the Firewalls in Sydney. Some customers may be experiencing intermittent connectivity loss at this time.

  4. identified Feb 04, 2026, 09:20 PM UTC

    After advice from FortiGate, we have been able to successfully reload one side of the HA FortiGate Firewall Cluster. We are reloading the opposite side now; there will be a brief outage of all traffic while this happens. The outage is expected to be 5-7 minutes Updates to follow

  5. identified Feb 04, 2026, 09:45 PM UTC

    The reload of the other side of the Fortigate Firewall cluster has not resulted in full connectivity for all services. Our Network and System Engineers are still reviewing this and we will update once we have further information.

  6. identified Feb 04, 2026, 09:48 PM UTC

    Most services have now been restored following the rollback and configuration restore. VPS Connectivity has been restored One final firewall reload is required to complete the work. During this reload, customers may experience a brief service interruption. Further updates will be provided shortly.

  7. monitoring Feb 04, 2026, 10:10 PM UTC

    All services have been restored. Firewall configurations have been restored from the backup taken prior to this morning's scheduled maintenance. The firewall cluster is now in sync, and all customer workloads are back online. Both firewalls are now running the latest firmware version. No further downtime is expected.

  8. resolved Feb 05, 2026, 11:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Servers Australia downtime and outages?

Pingoru polls Servers Australia's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Servers Australia reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Servers Australia alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Servers Australia for free

5 free monitors · No credit card required