Nexcess incident

Service Interruption - cloudhost-10358449.au-south-1.nxcli.net and cloudhost-10358510.au-south-1.nxcli.net

Minor Resolved View vendor source →

Nexcess experienced a minor incident on September 8, 2025 affecting au-south-1, lasting 19h 44m. The incident has been resolved; the full update timeline is below.

Started
Sep 08, 2025, 06:21 AM UTC
Resolved
Sep 09, 2025, 02:06 AM UTC
Duration
19h 44m
Detected by Pingoru
Sep 08, 2025, 06:21 AM UTC

Affected components

au-south-1

Update timeline

  1. investigating Sep 08, 2025, 06:21 AM UTC

    We are investigating a Service Interruption issue affecting the server cloudhost-10358449.au-south-1.nxcli.net and cloudhost-10358510.au-south-1.nxcli.net. Our Nexcess Systems Engineering team has been engaged and is actively working to restore service as quickly as possible. We appreciate your patience and understanding during this time. If you have any questions or concerns, please don’t hesitate to reach out via live chat or by opening a support case.

  2. identified Sep 08, 2025, 07:04 AM UTC

    Nexcess Systems Engineers have identified the root cause of the service interruption. We will provide another update as soon as more information becomes available. We thank you for your patience and understanding during this period. If you have any questions or concerns, please don’t hesitate to reach out via live chat or by opening a support case.

  3. identified Sep 08, 2025, 10:23 AM UTC

    cloudhost-10358510.au-south-1.nxcli.net - The server is back online and has remained stable so far. cloudhost-10358449.au-south-1.nxcli.net - The server is online, and we are restoring a few websites that are still showing errors. We will continue to update this page as progress is made.

  4. monitoring Sep 08, 2025, 02:44 PM UTC

    Both affected servers are back online and stable. We are monitoring performance and availability to ensure continued stability. If you have any questions or need further assistance, please don’t hesitate to contact us via live chat or by opening a support case.

  5. resolved Sep 09, 2025, 02:06 AM UTC

    This incident has been resolved.