Issue with Legacy Alert Delivery

Incident Report for Auvik Networks Inc.

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.
Posted Aug 17, 2026 - 12:42 EDT

Monitoring

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.
Posted Aug 17, 2026 - 12:38 EDT

Update

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
Posted Aug 17, 2026 - 12:24 EDT

Identified

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.
Posted Aug 17, 2026 - 11:24 EDT

Investigating

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.
Posted Aug 17, 2026 - 11:00 EDT
This incident affected: Network Mgmt (us1.my.auvik.com, us2.my.auvik.com, us3.my.auvik.com, us4.my.auvik.com, us5.my.auvik.com, us6.my.auvik.com, eu1.my.auvik.com, eu2.my.auvik.com, au1.my.auvik.com, ca1.my.auvik.com, lnx.my.auvik.com).