Auvik Networks Inc. Incident History

1. resolvedSep 3 · 12:18 UTC

   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.

Reported by Auvik Networks Inc. on their status page.

1. postmortemAug 28 · 15:21 UTC

   # 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.

Reported by Auvik Networks Inc. on their status page.

1. postmortemAug 24 · 17:54 UTC

   # Service Degradation - Legacy Alerts Notification ## Root Cause Analysis ### Duration of the incident Discovered: Aug 17, 2026 13:15 - UTC Resolved: Aug 21, 2026 14:12 - UTC ### Customer impact Some customers using Legacy Alerts experienced inaccurate alert notifications, including false-positive alerts and unintended email notifications. During remediation, some legacy alert processing was delayed, and alert visibility in the user interface temporarily lagged. V2 Alerts remained operational throughout the incident. ### Cause A product release intended to retire older default Legacy Alert configurations for new environments also removed supporting alert conditions that were still required by some existing customers with customized Legacy Alerts. Without the complete conditions, certain Legacy Alerts could trigger inaccurately. The remediation required reprocessing affected alerts, which temporarily increased processing load and contributed to delayed alert visibility, alert flapping, and excessive notifications. ### Effect Affected Legacy Alerts could trigger when the underlying condition was not present, re-trigger after being paused, or send notifications more broadly than intended. The resulting in-service lag also temporarily delayed displaying some alerts. Engineering restored the required alert configuration, removed the unintended broad email association, increased processing capacity, and proactively corrected additional affected customer environments. ### Future consideration\(s\) • Add monitoring for abnormal volumes of Legacy Alerts so unexpected alert activity can be detected earlier. • Expand pre-release and end-to-end testing for existing customized Legacy Alerts, including alert triggering, notification delivery, and post-change recovery behavior. • Strengthen canary-release review so alerting anomalies are investigated and understood before wider deployment.

Reported by Auvik Networks Inc. on their status page.

1. resolvedAug 17 · 16:42 UTC

   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.

Reported by Auvik Networks Inc. on their status page.