Vendor Status Watch

← all vendors

Auvik status history

Current state: operational — “All Systems Operational” per https://status.auvik.com (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.

3incidents, last 30 days
5incidents, last 90 days
22incidents on record
Incidents per week, last 12 weeks:

How long do Auvik incidents last?

2.0 hmedian incident duration21 measured
43.7 h90th percentile1 in 10 ran longer
80 minmedian, major/critical only4 incidents

From 21 incidents with a vendor-posted start and resolve time. Longest on record: Inaccurate notifications being sent for legacy alerts — 2.8 days (2026-08-17 17:53 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (22)

StartedIncidentStatusImpactDuration
2026-09-19 11:00 UTCScheduled Maintenancemaintenancemaintenance25 h 29 min (approx.)
2026-09-03 11:12 UTCIncident Titlepostmortemcritical1 h 05 min
2026-08-27 12:46 UTCService Disruption - AU1 Cluster Sitespostmortemmajor44 min
2026-08-17 17:53 UTCInaccurate notifications being sent for legacy alertspostmortemminor2 d 20 h
2026-08-17 15:00 UTCIssue with Legacy Alert Deliveryresolvedminor1 h 42 min
2026-04-14 00:32 UTCEmergency Collector Rollbackpostmortemminor2 h 01 min
2026-03-08 19:10 UTCService Degradation – Some Customers Experiencing Login Issues After Maintenancepostmortemminor26 h 15 min
2025-12-15 23:28 UTCEmergency maintenance for EU2postmortemminor2 h 29 min
2025-12-15 14:35 UTCMeraki Switch stacks creating duplicate devices in the productpostmortemminor3 h 47 min
2025-12-11 14:30 UTCDuplicate FortiNet firewalls created on the EU2 cluster.postmortemminor9 h 15 min
2025-12-05 12:50 UTCAuvik Live Chat is Inaccessibleresolvedminor42 min
2025-12-03 14:21 UTCService Disruption - Login issuesresolvedminor3 h 06 min
2025-11-21 18:29 UTCService Disruption - Reduced functionality across all clusterspostmortemminor56 min
2025-10-20 09:51 UTCPartial service degradation due to AWS outageresolvedminor1 h 06 min
2025-10-15 15:22 UTCClients on US4 cluster are experiencing 500 Errorspostmortemminor2 h 11 min
2025-09-23 17:45 UTCSite performance and access issuespostmortemmajor2 d 20 h
2025-09-17 13:53 UTCService Disruption - Log in issues to Auvikpostmortemminor31 h 06 min
2025-09-10 16:43 UTCUsers are having issues connecting to Auvikpostmortemnone43 min
2025-08-27 21:30 UTCUS4 clients are not accessibleresolvedmajor1 h 36 min
2025-08-25 18:32 UTCService Disruption - Auvik clients are experiencing a disruption of services - Multiple Clusterspostmortemnone43 h 41 min
2025-08-25 16:58 UTCSite Dropdown and permission issues in the Auvik UIpostmortemnone0 min
2025-08-22 09:32 UTCService Degraded - Clients on the EU1 cluster using V2 alerting are not reviewing device alertspostmortemminor1 h 04 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Auvik with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "auvik"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}