Auvik Networks Inc. Status Page

Sep 3, 2026 · resolved Sep 3

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

Aug 27, 2026 · resolved Aug 27

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

Aug 17, 2026 · resolved Aug 20

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

Aug 17, 2026 · resolved Aug 17

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.

Apr 14, 2026 · resolved Apr 14

# Service Disruption - SNMPv3 Monitoring Loss Following Collector Upgrade ## Root Cause Analysis ### Duration of the incident Discovered: Apr 13, 2026 20:00 - UTC Resolved: Apr 13, 2026 22:32 - UTC ### Customer impact Customers experienced a loss of monitoring data from only devices using specific SNMPv3 configurations. While devices remained online and reachable, monitoring data was not collected, resulting in reduced visibility across environments. ### Cause A recent collector upgrade introduced changes to encryption handling that affected support for certain legacy SNMPv3 configurations. This resulted in failures when attempting to collect data from devices configured that way. ### Effect Monitoring data collection failed for affected devices across multiple clusters. This led to a noticeable drop in available device metrics and visibility, despite no loss of connectivity to the devices themselves. ### Future consideation\(s\) * Expand test coverage to include a broader range of SNMP configurations * Improve monitoring to detect drops in data collection more proactively * Strengthen validation processes for major upgrades and dependency changes * Implement additional safeguards to identify compatibility issues prior to release

Is Auvik Networks Inc. down right now?

No — Auvik Networks Inc. is up. All systems operational as of Oct 12, 4:57 AM UTC.

What is Auvik Networks Inc.'s current status?

Auvik Networks Inc.: All Systems Operational. Alert24 checks Auvik Networks Inc.'s status page continuously and can notify you the moment it changes.

How do I get alerted when Auvik Networks Inc. goes down?

Alert24 monitors Auvik Networks Inc. and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.