Is Auvik down?

We are currently investigating reports of an outage affecting sites on the US4 cluster. Impact: Customers may experience loss of services on these sites All other clusters are functioning properly. Next Steps: Our team is working to identify contributing factors. We will share updates as more information becomes available.

Customer Impact: Customers on the US4 cluster may remain unable to access their sites while the system recovers. All other clusters are operating normally. Current Status: Our team has identified a potential cause of the outage and is applying mitigation measures. Next Steps: We are monitoring the system’s recovery and will provide another update as more information becomes available. If you continue to experience issues, please contact Auvik Support so we can track the impact and assist you.

Customer Impact: Customers on the US4 cluster may remain unable to access their sites while the system recovers. All other clusters are operating normally. Current Status: Sites are recovering properly and becoming available. Next Steps: We are monitoring the system’s recovery and will provide another update as more information becomes available. If you continue to experience issues, please contact Auvik Support so we can track the impact and assist you.

We have applied changes to address the issue. Services appear to be operating normally, with the remaining site recovering. We are monitoring closely for stability. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: We will post a final update once we confirm the resolution.

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.

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.

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.

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.

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.

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

We are investigating reports of a high volume of inaccurate notifications. Impact: Customers may experience improper alerts and notifications The following services are not affected: V2 alert notifications. Next Steps: Our team is working to identify contributing factors. We will share updates as more information becomes available.

We are continuing to investigate the issues with incorrect notifications being sent. Impact: Customers may experience improper alerts and notifications The following services are not affected: V2 alert notifications. Next Steps: Our team is working to identify contributing factors. We will share updates as more information becomes available.

Our team has identified a suspected cause of the incorrect notifications and is taking steps to fix the issue. Impact: Customers may continue to experience false paused notifications The following services are not affected: V2 alerting Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide progress updates.

We have applied changes to address the issue. Alert notifications should no longer be sent to unintended users We are closely monitoring services for stability. Impact: Services should be operating normally, though new alerts may be delayed in the UI until services catch up; if you continue to encounter problems, please report them to Auvik Support. Next Steps: We will post a final update once we confirm the resolution.

We have applied additional changes to address the issue causing alerts to not appear in the UI. We are seeing alerts gradually recover and are continuing to closely monitor services to ensure a full recovery. Impact: Alert notifications should no longer be sent to unintended users. Alerts may still be delayed in appearing in the UI as services continue to recover. If you continue to encounter problems, please report them to Auvik Support. Next Steps: We will continue monitoring alert recovery and service stability and will provide a final update once we confirm the issue is fully resolved.

We have observed a full recovery of the affected services, and alerts are now appearing in the UI as expected across all clusters. We are continuing to closely monitor services to ensure stability.

We are continuing to monitor for any further issues.

We continue to receive reports of unexpected emails being sent by legacy alerting. Our team is actively investigating the issue. Next Steps: We will provide another update as more information becomes available.

We continue investigating the legacy alerting issue causing unexpected email notifications. Our investigation has made progress, and we believe we are moving toward a resolution. We are continuing to validate our findings and work through the remaining steps. Next Steps: We will provide another update as we confirm the resolution or as additional information becomes available

We continue investigating the legacy alerting issue causing unexpected email notifications. We are continuing to validate our findings and work through the remaining steps. Next Steps: We will provide another update as we confirm the resolution or as additional information becomes available

We have continued to see stable alerting behaviour following the changes made earlier, and alerting services remain fully recovered. We are continuing to monitor closely to ensure ongoing stability. Impact: Services are operating normally. If you experience any unexpected alerting behaviour or other outliers, please report them to Auvik Support so our team can investigate. Next Steps: We will continue monitoring services and will provide a final update once we are confident the issue remains fully resolved.

We have continued to see stable alerting behavior overnight, and alerting services remain fully recovered. We are continuing to monitor closely to ensure ongoing stability. Impact: Services are operating normally. If you experience any unexpected alerting behavior or other outliers, please report them to Auvik Support so our team can investigate.

We have continued to see stable alerting behavior. We are continuing to monitor closely to ensure ongoing stability. Impact: Services are operating normally. If you experience any unexpected alerting behavior or other outliers, please report them to Auvik Support so our team can investigate.

We have continued to observe stable alerting behavior across all systems. Our engineering team will continue active monitoring through the day to ensure continued performance. Current Impact: All services are operating normally. Critical Reminder: If you experience any unexpected alerting behavior or identify other outliers, please report them immediately to Auvik Support for investigation.

We have continued to observe stable alerting behavior across all systems. Our engineering team will continue active monitoring and address any reported issues. Current Impact: All services are operating normally. Critical Reminder: If you experience any unexpected alerting behavior or identify other outliers, please report them immediately to Auvik Support for investigation.

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.

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

We are currently investigating reports of a flood of legacy alerts. Impact Default legacy alerts are temporarily not functioning as expected while we investigate. Customized legacy alerts may also be impacted. V2 alerts are currently working as expected. Next Steps Our team is actively investigating to identify the contributing factors. We will provide additional updates as more information becomes available.

Our team has identified a suspected cause of the legacy alerts not working properly and is taking steps to fix it. Impact: Customers may continue to experience legacy alerts not working The following services are not affected: V2 alerts Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide progress updates.

Our team has identified a suspected cause of the legacy alerts not working properly and is taking steps to fix it. Impact: Customers may continue to experience legacy alerts not working The following services are not affected: V2 alerts Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying the fix to the EU1 clustered clients currently

We have applied changes to address the issue. We are now rolling out service fixes and monitoring closely for stability. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: We will post a final update once we confirm the resolution.

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.