Service Disruption - AU1 Cluster Sites

Summary

Service Disruption - AU1 Cluster Sites

# Service Disruption - Availability Issues on the AU1 Cluster ## Root Cause Analysis ### Duration of the incident Discovered: Aug 27, 2026 12:20 - UTC Resolved: Aug 27, 2026 13:15 - UTC ### Customer impact Clients hosted in the AU1 region experienced a temporary interruption of Auvik services. Depending on the client, monitoring, alerting, collector connectivity, and access to the web interface were unavailable for up to approximately one hour. ### Cause A cascading failure in core platform services caused multiple service components to restart, including a central coordination component. This resulted in widespread client-environment restarts across the AU1 region. ### Effect Affected client environments became temporarily unavailable while services restarted. The platform recovered automatically. Post-recovery verification confirmed normal service operation. ### Future consideration\(s\) * Continue evaluating resiliency improvements for core service coordination and recovery behavior following large-scale restarts. * Continue using post-recovery validation checks to confirm client services return to expected operation after a broad service restart.

• Started

  Aug 27, 2026 · 8:46 AM

• Resolved

  Aug 27, 2026 · 9:30 AM

• Duration

  44m

• Severity

  Major

• ◐

  Investigating

  Aug 27 · 8:46 AM Auvik Networks

  We are investigating reports of availability issues affecting sites hosted on the AU1 cluster. Customer Impact Customers on the AU1 cluster may experience service interruptions. All other clusters are unaffected. Next Steps Our team is working to identify the contributing factors. We will share another update as we learn more.

• ◆

  Identified

  Aug 27 · 8:52 AM Auvik Networks

  Our team has identified a suspected cause of the availability issues affecting sites hosted on the AU1 cluster and is taking steps to resolve it. Impact Customers on the AU1 cluster may continue to experience service interruptions. All other clusters remain unaffected. Please report any related issues to Auvik Support so we can track them and provide further assistance. Next Steps We are applying mitigation measures and will provide updates on our progress.

• ◉

  Monitoring

  Aug 27 · 9:03 AM Auvik Networks

  Our team has applied mitigation measures, and we have restored availability for sites hosted on the AU1 cluster. Some sites continue to recover. We are monitoring the environment to confirm continued stability. Impact Customers should no longer experience service interruptions. All other clusters remain unaffected. Please report any related issues to Auvik Support so we can track them and provide further assistance. Next Steps We will continue monitoring and provide another update once we have confirmed the issue is fully resolved.

• ✓

  Resolved

  Aug 27 · 9:30 AM Auvik Networks

  The incident has been fully resolved, and all services are operating normally. Customers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support. We will provide a Root Cause Analysis (RCA) once it is available.

• ✓

  Postmortem

  Aug 28 · 11:21 AM Auvik Networks

  # Service Disruption - Availability Issues on the AU1 Cluster ## Root Cause Analysis ### Duration of the incident Discovered: Aug 27, 2026 12:20 - UTC Resolved: Aug 27, 2026 13:15 - UTC ### Customer impact Clients hosted in the AU1 region experienced a temporary interruption of Auvik services. Depending on the client, monitoring, alerting, collector connectivity, and access to the web interface were unavailable for up to approximately one hour. ### Cause A cascading failure in core platform services caused multiple service components to restart, including a central coordination component. This resulted in widespread client-environment restarts across the AU1 region. ### Effect Affected client environments became temporarily unavailable while services restarted. The platform recovered automatically. Post-recovery verification confirmed normal service operation. ### Future consideration\(s\) * Continue evaluating resiliency improvements for core service coordination and recovery behavior following large-scale restarts. * Continue using post-recovery validation checks to confirm client services return to expected operation after a broad service restart.