- Detected by Pingoru
- Aug 17, 2026, 03:00 PM UTC
- Resolved
- Aug 17, 2026, 04:42 PM UTC
- Duration
- 1h 42m
Affected: us1.my.auvik.comus2.my.auvik.comus3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.comlnx.my.auvik.com
Timeline · 5 updates
-
investigating Aug 17, 2026, 03:00 PM UTC
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.
-
identified Aug 17, 2026, 03:24 PM UTC
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.
-
identified Aug 17, 2026, 04:24 PM UTC
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
-
monitoring Aug 17, 2026, 04:38 PM UTC
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.
-
resolved Aug 17, 2026, 04:42 PM 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.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 12:32 AM UTC
- Resolved
- Apr 14, 2026, 02:33 AM UTC
- Duration
- 2h 1m
Affected: us1.my.auvik.comus2.my.auvik.comus3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.comlnx.my.auvik.com
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Mar 08, 2026, 07:10 PM UTC
- Resolved
- Mar 09, 2026, 09:26 PM UTC
- Duration
- 1d 2h
Affected: my.auvik.comus1.my.auvik.comAuvik TrafficInsightsus2.my.auvik.comSaaS ManagementAuvik Website (www.auvik.com)us3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.com
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 11:28 PM UTC
- Resolved
- Dec 16, 2025, 01:57 AM UTC
- Duration
- 2h 29m
Affected: eu2.my.auvik.com
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 02:35 PM UTC
- Resolved
- Dec 15, 2025, 06:23 PM UTC
- Duration
- 3h 47m
Affected: us1.my.auvik.comus2.my.auvik.comus3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.com
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Dec 11, 2025, 02:30 PM UTC
- Resolved
- Dec 11, 2025, 11:46 PM UTC
- Duration
- 9h 15m
Affected: eu2.my.auvik.com
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 12:50 PM UTC
- Resolved
- Dec 05, 2025, 01:32 PM UTC
- Duration
- 42m
Affected: Auvik Website (www.auvik.com)
Timeline · 3 updates
-
investigating Dec 05, 2025, 12:50 PM UTC
We are currently investigating reports of the Auvik chatbot not transferring the session to a live agent. Impact: Customers will not be able to reach a live agent until the service is restored. The following services are not affected: The Knowledge Base, Support Portal, and Auvik site. Please submit a web form ticket from the Support site in the meantime, if needed to contact support. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.
-
identified Dec 05, 2025, 01:17 PM UTC
Our team has identified a suspected cause of the Auvik chatbot not transferring the session to a live agent. Impact: Customers will not be able to reach a live agent until the service is restored. The following services are not affected: The Knowledge Base, Support Portal, and Auvik site. Please submit a web form ticket from the Support site in the meantime, if needed to contact support. 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 updates on progress.
-
resolved Dec 05, 2025, 01:32 PM 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 appreciate your understanding and patience.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 02:21 PM UTC
- Resolved
- Dec 03, 2025, 05:28 PM UTC
- Duration
- 3h 6m
Timeline · 3 updates
-
identified Dec 03, 2025, 02:21 PM UTC
Affected Services: Login We’re aware that an issue with Okta caused login failures for many users accessing Auvik. Okta has reported that the problem is resolved, but some users may still experience difficulties signing in. You can follow their updates here: https://status.okta.com/#incident/a9CWR00000012Cg2AI Recent status information is also available at: https://status.okta.com/#recent Impact: While we work on the resolution, users may continue to experience login issues Next Steps: Our team is actively working to resolve the issue and will provide updates as progress is made. Your patience is greatly appreciated, and we regret any inconvenience you may have experienced.
-
monitoring Dec 03, 2025, 03:54 PM UTC
Latest update from Okta December 3, 2025 at 7:50am PST Our service is seeing recovery following successful mitigation efforts with our provider. We continue to closely monitor system stability. Our next update will be in 30 minutes, or sooner if new information is available. We are watching our systems for recovery and performance.
-
resolved Dec 03, 2025, 05:28 PM UTC
Latest update from Okta Incident Resolved December 3, 2025 at 8:58am PST An issue impacting the core authentication service for customers in Okta Cell US7 has been resolved. Additional root cause information will be available within five business days. We will close the status page for Auvik's sites.
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 06:29 PM UTC
- Resolved
- Nov 21, 2025, 07:26 PM UTC
- Duration
- 56m
Affected: my.auvik.comus1.my.auvik.comus2.my.auvik.comus3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.com
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 09:51 AM UTC
- Resolved
- Oct 20, 2025, 10:57 AM UTC
- Duration
- 1h 6m
Affected: my.auvik.comus1.my.auvik.comAuvik TrafficInsightsus2.my.auvik.comSaaS ManagementAuvik Website (www.auvik.com)us3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.com
Timeline · 4 updates
-
identified Oct 20, 2025, 09:51 AM UTC
Auvik is currently being impacted by today’s AWS outage. Some pages and APIs may be slow or have errors. No data loss is expected. We will update here as we receive more information
-
monitoring Oct 20, 2025, 10:11 AM UTC
AWS services are recovering. Services appear to be operating normally, and 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: A final update will be posted once we confirm the resolution.
-
monitoring Oct 20, 2025, 10:42 AM UTC
AWS services are recovering. Services appear to be operating normally, and we are monitoring closely for stability. Amazon is recommending flushing your DNS cache if you are still experiencing issues. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.
-
resolved Oct 20, 2025, 10:57 AM 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.
Read the full incident report →
- Detected by Pingoru
- Oct 15, 2025, 03:22 PM UTC
- Resolved
- Oct 15, 2025, 05:33 PM UTC
- Duration
- 2h 11m
Affected: us4.my.auvik.com
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2025, 05:45 PM UTC
- Resolved
- Sep 26, 2025, 01:58 PM UTC
- Duration
- 2d 20h
Affected: my.auvik.comus1.my.auvik.comus2.my.auvik.comus3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.com
Timeline · 22 updates
Read the full incident report →
- Detected by Pingoru
- Sep 17, 2025, 01:53 PM UTC
- Resolved
- Sep 18, 2025, 09:00 PM UTC
- Duration
- 1d 7h
Affected: my.auvik.comus1.my.auvik.comus2.my.auvik.comus3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.com
Timeline · 9 updates
Read the full incident report →
Notice September 10, 2025 - Detected by Pingoru
- Sep 10, 2025, 04:43 PM UTC
- Resolved
- Sep 10, 2025, 05:26 PM UTC
- Duration
- 43m
Affected: my.auvik.comus1.my.auvik.comus2.my.auvik.comus3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.com
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2025, 09:30 PM UTC
- Resolved
- Aug 27, 2025, 11:06 PM UTC
- Duration
- 1h 36m
Affected: us4.my.auvik.com
Timeline · 4 updates
-
investigating Aug 27, 2025, 09:30 PM UTC
We are currently investigating reports of an outage affecting clients on US4. Impact: Customers may experience an inability to log in to their site The following services are not affected: Other clusters, including alerting and monitoring. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.
-
identified Aug 27, 2025, 09:38 PM UTC
Our team has identified a suspected cause of the outage on the US4 cluster and is taking steps to remediate the issue. Impact: Customers will not have access to the sites on the US4 cluster for the next two hours while we bring them online. Some sites on the US4 may become operational before that time. The following services are not affected: Sites on other clusters.. 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 updates on progress.
-
monitoring Aug 27, 2025, 10:38 PM UTC
We have applied changes to address the issue. Services appear to be starting up normally, and we are monitoring closely for stability. Impact: Services should be becoming available. The site will continue to come online over the next hour. If you encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.
-
resolved Aug 27, 2025, 11:06 PM UTC
The access issues for clients on the US4 cluster have been fully resolved, and services are operating as expected. Impact: Customers should no longer experience any related issues. If you continue to experience issues, please report them to Auvik Support.
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2025, 06:32 PM UTC
- Resolved
- Aug 27, 2025, 02:13 PM UTC
- Duration
- 1d 19h
Affected: us1.my.auvik.comus2.my.auvik.comus3.my.auvik.comus4.my.auvik.comus5.my.auvik.comus6.my.auvik.comeu1.my.auvik.comeu2.my.auvik.comau1.my.auvik.comca1.my.auvik.com
Timeline · 18 updates
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2025, 04:58 PM UTC
- Resolved
- Aug 25, 2025, 04:58 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Aug 22, 2025, 09:32 AM UTC
- Resolved
- Aug 22, 2025, 10:36 AM UTC
- Duration
- 1h 4m
Affected: eu1.my.auvik.com
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2025, 01:50 PM UTC
- Resolved
- Aug 20, 2025, 02:09 PM UTC
- Duration
- 18m
Affected: eu2.my.auvik.com
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 03:30 PM UTC
- Resolved
- Aug 19, 2025, 03:30 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2025, 05:21 PM UTC
- Resolved
- Jul 31, 2025, 01:40 PM UTC
- Duration
- 3d 20h
Affected: us4.my.auvik.com
Timeline · 17 updates
Read the full incident report →
- Detected by Pingoru
- Jul 26, 2025, 04:43 PM UTC
- Resolved
- Jul 27, 2025, 11:51 AM UTC
- Duration
- 19h 7m
Affected: us1.my.auvik.comus4.my.auvik.comau1.my.auvik.com
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Jul 25, 2025, 07:24 PM UTC
- Resolved
- Jul 25, 2025, 09:13 PM UTC
- Duration
- 1h 49m
Affected: us3.my.auvik.com
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jul 03, 2025, 05:14 PM UTC
- Resolved
- Jul 03, 2025, 06:44 PM UTC
- Duration
- 1h 30m
Affected: us3.my.auvik.com
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2025, 12:19 PM UTC
- Resolved
- Jun 11, 2025, 12:00 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →