Addigy status history
Current state: operational — “All Systems Operational” per https://status.addigy.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Addigy incidents last?
From 12 incidents with a vendor-posted start and resolve time. Longest on record: Addigy Identity: "Something went wrong" error affecting some users — 5.9 days (2026-07-09 21:09 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 (13)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-12 11:00 UTC | Addigy Cloud Maintenance | maintenance | maintenance | 25 h 30 min (approx.) |
| 2026-08-20 14:04 UTC | Post-Maintenance Login and Data Viewing Issues | resolved | major | 1 h 49 min |
| 2026-08-03 16:08 UTC | Addigy Cloud Interface Unavailable | resolved | none | 4 min |
| 2026-08-03 16:01 UTC | Issue affecting Apple Push Notification service (APNs) certificates | resolved | none | 52 min |
| 2026-07-09 21:09 UTC | Addigy Identity: "Something went wrong" error affecting some users | resolved | minor | 5 d 21 h |
| 2026-06-22 14:15 UTC | Elevated Latency on Addigy Cloud Interface | resolved | minor | 3 h 45 min |
| 2026-06-18 12:53 UTC | Issue with direct agent installer download links on Add Devices page | resolved | major | 7 min |
| 2026-03-17 21:11 UTC | Addigy Cloud Interface Unavailable | resolved | critical | 1 h 54 min |
| 2026-02-22 18:41 UTC | Trouble logging in | resolved | critical | 1 h 34 min |
| 2026-01-30 14:27 UTC | Trouble logging in | resolved | critical | 2 h 31 min |
| 2025-09-30 17:34 UTC | Issues with Device Filtering and Device Searching | resolved | major | 44 min |
| 2025-09-09 18:50 UTC | Trouble logging into Addigy Platform | resolved | critical | 49 min |
| 2025-08-21 18:14 UTC | Elevated Latency on Addigy Cloud Interface | resolved | minor | 1 h 32 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 Addigy with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"addigy"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}