Is Auvik down?

We will be upgrading the Auvik cloud. The session will take about three hours. During this time, you may not be able to log into Auvik. There may also be interruptions to your network monitoring. If you have any questions, please use the Support button at the bottom right in Auvik.

Most tenants have recovered, we are waiting on remaining tenants to come back up. We are monitoring the situation to ensure stability and confirm that the service remains fully functional. Next Steps: We will provide a final update once the issue is resolved. Thank you for your patience, and we apologize for any inconvenience caused.

The incident has been fully resolved. Regular service has been restored, and all systems operate as expected. Impact: Users should no longer experience any issues related to the service disruption. If you are still experiencing issues, please do not hesitate to reach out to the support team and update your ticket or report any problems you haven't reported yet. Service has been fully restored. We apologize for any disruption to our services. We thank you for your understanding. If you continue to experience issues, please don't hesitate to contact our support team. We will post an RCA after an internal investigation.

# Service Disruption - Monitoring Platform Unavailability US4 Cluster ## Root Cause Analysis ### Duration of the incident Discovered: Oct 25, 2026 11:33 - UTC Resolved: Oct 25, 2026 14:00 - UTC ### Customer impact Clients experienced a total loss of access to the web interface and a suspension of network monitoring services for approximately 2.5 hours. ### Cause During scheduled maintenance, a procedural oversight affected a service configuration in the US4 region. ### Effect The unplanned change caused instability in the US4 cluster, making the user interface and monitoring capabilities unavailable. ### Future consideration\(s\) * Review the maintenance procedure and clarify the checks required before changes are made. * Enhance monitoring visibility for the on-call team to ensure faster identification of regional service degradation.

We will be upgrading the Auvik cloud. The session will take about three hours. During this time, you may not be able to log into Auvik. There may also be interruptions to your network monitoring. If you have any questions, please use the Support button at the bottom right in Auvik.

The incident has been fully resolved. Regular service has been restored, and all systems operate as expected. Impact: Users should no longer experience any issues related to the service disruption. If you are still experiencing issues, please do not hesitate to reach out to the support team and update your ticket or report any problems you haven't reported yet. Service has been fully restored. We apologize for any disruption to our services.  We thank you for your understanding. If you continue to experience issues, please don't hesitate to contact our support team. We will post an RCA after an internal investigation.

# Service Disruption - Regional Monitoring Platform Unavailability ## Root Cause Analysis ### Duration of the incident Discovered: Oct 23, 2026 23:54 - UTC Resolved: Oct 24, 2026 05:30 - UTC ### Customer impact Clients experienced intermittent unavailability of the web interface and network monitoring services for approximately six hours. During this time, users were intermittently unable to access the dashboard or receive real-time monitoring updates. ### Cause A backend service node became overloaded, leading to the unexpected disconnection of a critical system tenant. This triggered a cascading failure across the service cluster, causing multiple nodes to enter a failure state and preventing the coordination service from successfully re-establishing the cluster. ### Effect The service cluster entered a continuous failure loop, resulting in a total loss of connectivity for the web UI and monitoring agents until a full manual cluster restart was performed. ### Future consideration\(s\) * Improve automated recovery procedures to handle scenarios where the primary coordination service enters a failure loop. * Review and update internal documentation for cluster recovery to include specific steps for unblocking stuck deployments.

We are aware of the recently disclosed PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619. THE AUVIK PRODUCT DOES NOT DIRECTLY USE PHP We are reviewing our broader environments for potential exposure and will share updates as more information becomes available.

We are aware of the recently disclosed PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619. THE AUVIK PRODUCT DOES NOT DIRECTLY USE PHP. We have completed our review of our broader environments and have addressed any other potential exposures. No further updates are expected.

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.

# Service Disruption - US4 service interruption ## Root Cause Analysis ### Duration of the incident Discovered: Sep 03, 2026 07:05 UTC Resolved: Sep 03, 2026 12:20 UTC ### Customer impact Customers hosted in the US4 environment experienced intermittent service availability while the system was unstable. Impacts included difficulty accessing sites and the user interface, along with interruptions to monitoring visibility. ### Cause A core component in the US4 environment became unavailable. The platform's automated recovery process did not fully stabilize the environment, which led to repeated reconnection and recovery activity. A full restart of the US4 environment was required to restore normal operation. ### Effect The instability prevented parts of the US4 environment from communicating reliably. This caused service interruptions for many customers until the environment restarted and customer sites recovered. ### Future consideration\(s\) * Improve resilience and redundancy for critical components involved in environment recovery. * Strengthen automated monitoring and paging so this failure pattern is identified and escalated more quickly. * Review recovery behavior to reduce the likelihood that a similar component failure requires a full environment restart.

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.