Servers Australia Outage History

Servers Australia is up right now

Servers Australia had 31 outages in the last 2 years totaling 543h 27m of downtime — averaging 1.3 incidents per month.

There were 31 Servers Australia outages since November 4, 2025 totaling 543h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Notice September 28, 2026

MySAU Portal Connectivity

Detected by Pingoru
Sep 28, 2026, 06:15 AM UTC
Resolved
Sep 28, 2026, 06:38 AM UTC
Duration
23m
Affected: MySAU Customer Portal
Timeline · 2 updates
  1. investigating Sep 28, 2026, 06:15 AM UTC

    We are aware of issues presently affecting access to the MySAU Portal Services and engineers are investigating the cause. Customers may experience difficulty accessing their accounts, lodging cases, viewing services and anything similar that involves this platform. Further updates will be provided when available. Anybody that needs urgent assistance can contact Support via phone on 1300 788 862

  2. resolved Sep 28, 2026, 06:38 AM UTC

    Engineers have resolved the problem and the MySAU Portal & accompanying services are now back online.

Read the full incident report →

Notice September 21, 2026

Sydney-Perth Intercapital Backhaul high latency

Detected by Pingoru
Sep 21, 2026, 07:05 PM UTC
Resolved
Sep 22, 2026, 01:40 AM UTC
Duration
6h 34m
Affected: PerthEquinix PE2
Timeline · 3 updates
  1. investigating Sep 21, 2026, 07:05 PM UTC

    Servers Australia are aware of a high latency event on our Sydney-Perth intercapital backhaul, and are currently investigating.

  2. monitoring Sep 21, 2026, 07:06 PM UTC

    High latency only appears to affect one intercapital path. Engineers have preferred a different path, and backhaul latency has returned to normal. Backhaul provider is being contacted to understand the cause of the issue.

  3. resolved Sep 22, 2026, 01:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 16, 2026

Intermittent Service Disruption - Support Cases

Detected by Pingoru
Sep 16, 2026, 08:55 AM UTC
Resolved
Sep 16, 2026, 10:27 PM UTC
Duration
13h 32m
Affected: MySAU Customer Portal
Timeline · 3 updates
  1. investigating Sep 16, 2026, 08:55 AM UTC

    Engineers are investigating a unexpected intermittent service disruption with the support case system within the MySAU portal. Further works are underway to identify the source of the disruption, and updates will be provided as soon as possible.

  2. identified Sep 16, 2026, 10:34 AM UTC

    Engineers have identified a core system component experiencing increased load that has limited capacity. They are working on a fix to resolve the intermittent service disruption affecting customers access to support cases through the MySAU portal. No ETA is currently available for the implementation of the fix. If you require urgent & immediate support, please call our support team on 1300 788 862.

  3. resolved Sep 16, 2026, 10:27 PM UTC

    The Support Case system is since back online and working as expected, customers who raised or replied to cases during the period of September 16th 19:00 AEST through to September 17th 06:00 AEST are advised to check that their submissions went through successfully. Any customers that are continuing to experience problems, Support is available 24/7 through 1300 788 862 Option 2.

Read the full incident report →

Notice September 2, 2026

Service Disruption to Rack 0402 in Equinix SY4

Detected by Pingoru
Sep 02, 2026, 03:30 PM UTC
Resolved
Sep 02, 2026, 07:56 PM UTC
Duration
4h 25m
Affected: Equinix SY4Dedicated Servers
Timeline · 5 updates
  1. investigating Sep 02, 2026, 03:30 PM UTC

    Engineers are investigating monitoring reports of several services in a rack impacted in the Equinix SY4 datacentre. Further works are underway to identify the source of the disruption and updates will be provided as soon as possible.

  2. identified Sep 02, 2026, 03:36 PM UTC

    A power rail for the rack has been identified as the source of the disruption and we are now working with Equinix to get this resolved as soon as possible.

  3. identified Sep 02, 2026, 04:36 PM UTC

    Equinix Facilities Engineer and Smart Hands have confirmed that the breaker for the rail is re-tripping when reset, and are now working to identify and isolate the failed unit to restore power to the rail.

  4. identified Sep 02, 2026, 04:57 PM UTC

    The fault has been isolated to a single server, which was causing the rack power rail breaker to trip. That server has now been isolated and power has been successfully restored to the remainder of the rack. The affected server has not powered back up following restoration of power. An engineer is now travelling to the Equinix SY4 datacentre with replacement hardware to attend to the server and restore service. Further updates will be provided as work progresses.

  5. resolved Sep 02, 2026, 07:56 PM UTC

    The failed server's PSU has been replaced, and returned to service. All affected services in Rack 0402 have been restored.

Read the full incident report →

Notice September 2, 2026

Reduced Redundancy & Capacity - New Zealand

Detected by Pingoru
Sep 02, 2026, 02:08 AM UTC
Resolved
Sep 03, 2026, 03:06 AM UTC
Duration
1d
Affected: NetworkNew ZealandVocus - Albany
Timeline · 4 updates
  1. investigating Sep 02, 2026, 02:08 AM UTC

    We are investigating an issue affecting one of our transit interfaces in New Zealand. We have escalated the incident to our upstream provider and are currently awaiting their findings. While all services remain fully operational with no impact to end users, this Point of Presence (POP) is currently running with reduced capacity and redundancy.

  2. identified Sep 02, 2026, 02:11 AM UTC

    Our upstream provider has advised that this is a known issue and are working on restoration efforts.

  3. monitoring Sep 02, 2026, 03:16 AM UTC

    The upstream provider has restored the affected connection. Services continue to remain stable. We will monitor the situation and provide any updates as available.

  4. resolved Sep 03, 2026, 03:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 4, 2026

Reduced Capacity/Redundancy - SYD2

Detected by Pingoru
Aug 04, 2026, 02:55 PM UTC
Resolved
Aug 04, 2026, 11:49 PM UTC
Duration
8h 54m
Affected: SydneyNetworkSYD2
Timeline · 3 updates
  1. investigating Aug 04, 2026, 02:55 PM UTC

    Engineers are currently investigating a link failure between our Sydney POP and the SYD2 facility. There is no service impact at this time due to a second active link forwarding traffic. We are escalating to our vendor for further investigation.

  2. identified Aug 04, 2026, 03:55 PM UTC

    Engineers have been advised that this relates to planned maintenance activity with the circuit expected to be back online within the next few hours.

  3. resolved Aug 04, 2026, 11:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 16, 2026

Further Configuration Issues with Sydney Firewall Cluster

Detected by Pingoru
Jul 16, 2026, 02:33 AM UTC
Resolved
Jul 16, 2026, 04:01 PM UTC
Duration
13h 27m
Affected: SydneyFirewall
Timeline · 3 updates
  1. investigating Jul 16, 2026, 02:33 AM UTC

    We are currently reinvestigating our Sydney firewall cluster after experiencing a recurrence of the configuration limitations observed yesterday. While live customer network traffic continues to flow normally, attempts to modify platform configurations may fail or time out. Engineers are working again with our vendor, and updates will be provided as soon as they become available.

  2. identified Jul 16, 2026, 11:02 AM UTC

    Following an investigation with our vendor, we have determined that the ongoing issues are caused by two software bugs present in our current firewall firmware version. As the vendor's patch for this specific version is not expected until late next month, we have decided to upgrade the cluster to the next major firmware version as a priority. Details regarding this major upgrade window will be published ASAP. In the interim, we will be scheduling an emergency maintenance window for tomorrow morning to temporarily clear the current configuration limitations. A separate notification detailing tomorrow's exact schedule will be sent shortly. As a reminder, live customer network traffic remains fully stable and unaffected.

  3. resolved Jul 16, 2026, 04:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 15, 2026

Configuration Issues with Sydney Firewall Cluster

Detected by Pingoru
Jul 15, 2026, 12:15 AM UTC
Resolved
Jul 16, 2026, 01:25 AM UTC
Duration
1d 1h
Affected: SydneyFirewall
Timeline · 5 updates
  1. investigating Jul 15, 2026, 12:15 AM UTC

    Engineers are currently investigating an issue with our Sydney FortiGate firewall cluster that has resulted in configuration changes being temporarily restricted to read-only mode. Further updates will be provided ASAP.

  2. investigating Jul 15, 2026, 12:41 AM UTC

    Engineers have engaged our vendor support for further assistance.

  3. investigating Jul 15, 2026, 01:37 AM UTC

    Engineers are continuing to collaborate with our vendor on a resolution. We expect to provide the next update shortly.

  4. identified Jul 15, 2026, 03:50 AM UTC

    Following diagnostic review with our vendor, we will be conducting emergency maintenance to trigger a cluster failover and reboot of the primary unit. Please note that configuration changes may fail or experience intermittent errors until the reboot is completed. A dedicated status notification with scheduling details will be sent shortly.

  5. resolved Jul 16, 2026, 01:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 20, 2026

Sydney-Brisbane Intercapital backhaul fibre cut

Detected by Pingoru
Jun 20, 2026, 12:46 AM UTC
Resolved
Jun 22, 2026, 11:53 PM UTC
Duration
2d 23h
Affected: SydneyNetworkBrisbane
Timeline · 3 updates
  1. identified Jun 20, 2026, 12:46 AM UTC

    Engineers are aware of another incident causing disruption to one of our fibre paths between Sydney and Brisbane. No impact is expected as a result of this incident, though it should be noted that capacity between regions will be reduced. The incident occurred at approximately 06:37:08 AEST. No ETR has been provided.

  2. monitoring Jun 21, 2026, 01:57 AM UTC

    This connection was restored as of 21:51:03. We will monitor the situation until Monday morning, and provide an update once we are satisfied that the connection is stable.

  3. resolved Jun 22, 2026, 11:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 16, 2026

Sydney-Brisbane Intercapital backhaul service interruption

Detected by Pingoru
Jun 16, 2026, 05:12 AM UTC
Resolved
Jun 18, 2026, 04:58 AM UTC
Duration
1d 23h
Affected: SydneyNetworkBrisbaneEquinix SY4NextDC B1
Timeline · 6 updates
  1. investigating Jun 16, 2026, 05:12 AM UTC

    Servers Australia are aware of a fibre transmission issue impacting one of our backhaul links between Sydney and Brisbane. The issue has been escalated to our provider who are presently investigating. The issue was observed at approximately 03:52:15 UTC and is still ongoing. No service impact is expected as there are multiple redundant paths available between regions, though it should be noted that capacity and redundancy are reduced at this time.

  2. identified Jun 16, 2026, 05:24 AM UTC

    The fibre provider has dispatched a technician to the suspected location of the fault and will provide updates as available. The current ETA is 20:00 AEST and no ETR has been provided until the situation has been assessed.

  3. identified Jun 16, 2026, 02:16 PM UTC

    Upstream fibre ops team on site and has identified cable damaged during civil works. Assessment of the situation is continuing and no current ETR is available. We will provide our next update by 10 AM AEST.

  4. identified Jun 16, 2026, 11:52 PM UTC

    Upstream provider has advised that there are two breaks that need rejoining and some intermediate cable to be laid before services can be restored. The current ETR is 13:00 AEST, and we will provide updates as available.

  5. monitoring Jun 17, 2026, 03:44 AM UTC

    The fibre splicing has been completed and connectivity has been restored as of 12:26:54 AEST. Engineers will monitor the status of the link for stability and errors. Once we are satisfied that this link is stable, we will mark this incident as resolved.

  6. resolved Jun 18, 2026, 04:58 AM UTC

    Engineers have monitored the status of the link overnight and are satisfied that the connection remains stable. This incident is now resolved.

Read the full incident report →

Notice May 26, 2026

Equinix BR1 - Colocation rack switch issue

Detected by Pingoru
May 26, 2026, 02:04 AM UTC
Resolved
May 27, 2026, 04:44 AM UTC
Duration
1d 2h
Affected: NetworkBrisbaneEquinix BR1
Timeline · 3 updates
  1. identified May 26, 2026, 02:04 AM UTC

    An issue has been identified with a colocation switch in the Equinix BR1 facility, specifically rack BR1:02:040110:0511 which is affecting connectivity to services within this rack. On-site technicians are working on restoring service to this rack, and we will provide updates as available.

  2. monitoring May 26, 2026, 02:31 AM UTC

    On-site technicians have replaced failed components and services should be returning to normal. If you continue to experience issues as a result of this incident, feel free to raise a case via the MySAU portal. We will monitor the situation and mark this incident as resolved once we are satisfied the issue is no longer present.

  3. resolved May 27, 2026, 04:44 AM UTC

    After monitoring overnight, we are satisfied that the issue with this device has been resolved.

Read the full incident report →

Notice May 23, 2026

Reduced Network Capacity

Detected by Pingoru
May 23, 2026, 06:14 AM UTC
Resolved
May 24, 2026, 11:19 PM UTC
Duration
1d 17h
Affected: SydneyNetworkBrisbaneMelbournePerth
Timeline · 3 updates
  1. investigating May 23, 2026, 06:14 AM UTC

    We are currently investigating an issue affecting our BGP sessions with one of our IP transit providers, which have temporarily dropped due to an ongoing DDoS attack. Please note that no service impact or downtime is expected. While our network automatically rerouted traffic to ensure continuous uptime, we are currently running at reduced capacity. Our engineering team is actively working to mitigate the attack and restore all sessions as quickly as possible.

  2. monitoring May 23, 2026, 06:26 AM UTC

    All affected BGP sessions have been successfully restored, and network capacity has returned to full strength. Our team is currently monitoring the situation closely to ensure ongoing stability and performance.

  3. resolved May 24, 2026, 11:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 23, 2026

Packet Loss Affecting Some International Connectivity

Detected by Pingoru
May 23, 2026, 12:31 AM UTC
Resolved
May 24, 2026, 11:19 PM UTC
Duration
1d 22h
Affected: Network
Timeline · 6 updates
  1. investigating May 23, 2026, 12:31 AM UTC

    Network engineers have been alerted to packet loss affecting connectivity to our network from some international locations. Further updates will be provided as soon as more information becomes available.

  2. investigating May 23, 2026, 12:55 AM UTC

    Upstream engineers have identified the issue, and are working towards a resolution. While the provider works to resolve this on their side, we are making routing changes within our network to prefer alternate paths and reduce the impact to customers.

  3. monitoring May 23, 2026, 02:30 AM UTC

    We have confirmed that packet loss is no longer occurring and are continuing to monitor connectivity to ensure services remain stable before closing this incident.

  4. identified May 23, 2026, 03:29 AM UTC

    There appears to be some packet loss to destinations routed via Hetzner cloud in Frankfurt (this includes Hetzner US). Engineers are investigating.

  5. monitoring May 23, 2026, 06:20 AM UTC

    The upstream transit provider has advised that the issue has now been resolved. We have confirmed that packet loss is no longer occurring and are continuing to monitor connectivity to ensure services remain stable

  6. resolved May 24, 2026, 11:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 19, 2026

Reduced Redundancy - Syncom SYD2

Detected by Pingoru
May 19, 2026, 12:31 PM UTC
Resolved
May 19, 2026, 11:39 PM UTC
Duration
11h 8m
Affected: SYD2
Timeline · 2 updates
  1. investigating May 19, 2026, 12:31 PM UTC

    Network engineers have been alerted to the loss of one of our redundant paths connecting the Syncom SYD2 facility to our Sydney SY1 facility. Engineers are investigating No services are expected to be affected by this due to a redundant path in place.

  2. resolved May 19, 2026, 11:39 PM UTC

    This incident has been resolved.

Read the full incident report →

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 January 23, 2026

Power issue, site on generator - Equinix SY1

Detected by Pingoru
Jan 23, 2026, 01:38 PM UTC
Resolved
Jan 23, 2026, 03:42 PM UTC
Duration
2h 3m
Affected: Equinix SY1Sydney
Timeline · 3 updates
  1. investigating Jan 23, 2026, 01:38 PM UTC

    We have observed an issue with power affecting the Equinix SY1 facility at approximately 00:15 AEDT. The current status from the facility team indicates that the site is partially running on generator. Engineers are currently investigating the impact while we await further information Further updates will be provided as available. If you have any questions please raise a case via the MySAU portal.

  2. monitoring Jan 23, 2026, 03:17 PM UTC

    The the grid supplier for the site has provided an estimated time of 3:30 AEDT for restoration of the utility supply. The site team have confirmed that all loads remain fully operational on generator until the utility supply is restored. Further updates will be provided as they are made available.

  3. resolved Jan 23, 2026, 03:42 PM UTC

    The Equinix SY1 site team have provided an update to confirm that the site is once again running on utility supply. All services remain operational. If you have any questions please raise a case via the MySAU portal.

Read the full incident report →

Minor January 10, 2026

Reduced Redundancy - Equinix PE2

Detected by Pingoru
Jan 10, 2026, 11:46 AM UTC
Resolved
Jan 14, 2026, 05:45 AM UTC
Duration
3d 17h
Affected: NetworkPerthEquinix PE2
Timeline · 7 updates
  1. identified Jan 10, 2026, 11:46 AM UTC

    We have been alerted to a fault affecting one of our upstream transit connections in the Equinix PE2 data centre. The issue has been escalated to the upstream provider for further investigation. No services are currently impacted, as traffic has successfully failed over to our secondary transit provider. Network redundancy is currently reduced while this issue is being investigated.

  2. identified Jan 10, 2026, 11:50 AM UTC

    Our upstream provider has confirmed that this is related to an unscheduled outage on their end and are currently investigating. Further updates will be provided as we hear from them.

  3. monitoring Jan 11, 2026, 12:19 AM UTC

    The upstream provider has resolved the incident. We will monitor for 24 hours before setting this incident to resolved.

  4. identified Jan 11, 2026, 02:15 AM UTC

    Our session with this provider is still continuing to flap. We've reached out to them again advising this and are awaiting a response.

  5. identified Jan 11, 2026, 09:21 AM UTC

    Our upstream provider has advised that the root cause of the service outage has been identified and a replacement unit is being prepared to resolve the issue. They expect service restoration by 10.00 AM AEDT 12/01/2026, though this timeframe remains subject to change. We will provide further updates when possible.

  6. monitoring Jan 11, 2026, 10:41 PM UTC

    Our provider has confirmed that service has been restored. As such, we've re-enabled our sessions, and they have established again. We will continue to monitor this for 24 hours before marking this incident as resolved.

  7. resolved Jan 14, 2026, 05:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 23, 2025

Loss of Networking - BR1:Rack 0508

Detected by Pingoru
Dec 23, 2025, 02:18 AM UTC
Resolved
Dec 23, 2025, 07:56 AM UTC
Duration
5h 38m
Affected: Equinix BR1
Timeline · 2 updates
  1. monitoring Dec 23, 2025, 02:18 AM UTC

    A customer in the shared colocation environment caused a broadcast storm due to a network loop within their equipment. This resulted in a brief network disruption affecting the shared switch for rack 0508. The affected switch port has been administratively disabled to isolate the issue. Network connectivity has now been fully restored to the edge switch in rack 0508. Our team is monitoring the environment to ensure continued stability. The customer has been advised on remediation steps to prevent recurrence.

  2. resolved Dec 23, 2025, 07:56 AM UTC

    Our Network Engineers have continued to monitor the affected switch throughout the day, with no further issues reported. Network services remain stable, and the incident is confirmed as resolved.

Read the full incident report →

Major December 10, 2025

Servers Australia Portal Connectivity Issues

Detected by Pingoru
Dec 10, 2025, 01:47 AM UTC
Resolved
Dec 10, 2025, 02:44 AM UTC
Duration
57m
Affected: MySAU Customer Portal
Timeline · 2 updates
  1. investigating Dec 10, 2025, 01:47 AM UTC

    Engineers are currently aware of connectivity issues affecting our MySAU / Servers Australia Customer Portal. Customers may have difficulty loading the pages and logging into their Servers Australia accounts. Further updates will be provided as soon as possible

  2. resolved Dec 10, 2025, 02:44 AM UTC

    Engineers have since resolved the issues relating to MySAU Portal connectivity, customers will be able to access their accounts and Support ticketing systems as normal. Customers who are still experiencing issues relating to this may need to clear their browser cache / use a Private Browsing session or alternative device, otherwise feel free to contact our Support team for assistance.

Read the full incident report →

Minor December 9, 2025

Process Crash on Sydney Routers

Detected by Pingoru
Dec 09, 2025, 04:09 AM UTC
Resolved
Dec 09, 2025, 10:46 AM UTC
Duration
6h 37m
Affected: Equinix SY1SydneyNetworkEquinix SY3Equinix SY4
Timeline · 3 updates
  1. investigating Dec 09, 2025, 04:09 AM UTC

    Network engineers are investigating a process crash affecting BGP on our Sydney routers. We believe that services should be operational and that this was just a momentary interruption. Further updates will be provided ASAP.

  2. monitoring Dec 09, 2025, 04:39 AM UTC

    Engineers have confirmed that the BGP process is stable, though we will continue to monitor the situation.

  3. resolved Dec 09, 2025, 10:46 AM UTC

    We believe this to have been the result of a software bug and as such will be scheduling firmware updates in the new year post embargo for these devices.

Read the full incident report →

Notice December 9, 2025

Equinix PE2 - Reduced transit redundancy

Detected by Pingoru
Dec 09, 2025, 03:19 AM UTC
Resolved
Dec 09, 2025, 06:14 AM UTC
Duration
2h 55m
Affected: NetworkPerthEquinix PE2
Timeline · 2 updates
  1. monitoring Dec 09, 2025, 03:19 AM UTC

    Engineers have identified an optical module in a pre-failure state and are working with technicians to replace the module. The module being replaced is used to connect to one of our upstream transit providers. No interruption to service is expected, though redundancy will be reduced until this work is completed. We will provide further updates as available, and set this status to resolved when work is concluded.

  2. resolved Dec 09, 2025, 06:14 AM UTC

    Whilst replacing the optic the technician inadvertently caused an interruption to traffic for services within Equinix PE2. We have resolved the connectivity issue and postponed additional works regarding this module replacement. The approximate window was between 05:39:05 and 05:46:00 UTC +0. If you experienced any issues during this period or have any questions, please get in contact with our Support team.

Read the full incident report →