Servers Australia incident

Reduced Redundancy - Equinix PE2

Minor Resolved View vendor source →

Servers Australia experienced a minor incident on January 10, 2026 affecting Network and Perth and 1 more component, lasting 3d 17h. The incident has been resolved; the full update timeline is below.

Started
Jan 10, 2026, 11:46 AM UTC
Resolved
Jan 14, 2026, 05:45 AM UTC
Duration
3d 17h
Detected by Pingoru
Jan 10, 2026, 11:46 AM UTC

Affected components

NetworkPerthEquinix PE2

Update timeline

  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.