Ninety status history
Current state: operational — “All Systems Operational” per https://status.ninety.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Ninety incidents last?
From 14 incidents with a vendor-posted start and resolve time. Longest on record: Microsoft To-Do Integration: Service Degraded — 18.0 days (2026-06-12 18:25 UTC). Excluded, never estimated: nothing. 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 (14)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-27 15:40 UTC | Quarterly and Annual 1:1s unable to load | resolved | minor | 23 min |
| 2026-08-27 13:07 UTC | Quarterly and Annual 1:1s having issues | resolved | minor | 4 min |
| 2026-07-16 13:25 UTC | Signups Currently Unavailable | resolved | minor | 19 min |
| 2026-06-12 18:25 UTC | Microsoft To-Do Integration: Service Degraded | resolved | minor | 17 d 22 h |
| 2026-05-21 17:01 UTC | Accountability Chart - Some companies experiencing errors | resolved | major | 2 h 55 min |
| 2026-05-11 18:07 UTC | Zapier Integration - Some users experiencing rate limiting | resolved | major | 1 h 17 min |
| 2026-01-12 15:26 UTC | Users Unable to Create Rocks | resolved | major | 31 min |
| 2025-12-03 14:26 UTC | Inviting users having issues | resolved | major | 3 h 48 min |
| 2025-12-02 20:19 UTC | Signing up and inviting new customers failing | resolved | major | 5 h 50 min |
| 2025-10-20 17:25 UTC | Live Chat Support Latency | resolved | minor | 5 h 04 min |
| 2025-10-20 16:35 UTC | Some clients are experiencing latency or message failure issues with Maz | resolved | minor | 20 h 25 min |
| 2025-08-26 13:10 UTC | Login Failures | resolved | major | 50 min |
| 2025-08-22 14:39 UTC | users logging in with eos.ninety.io experiencing issues | resolved | minor | 2 h 30 min |
| 2025-08-18 14:22 UTC | Microsoft Single Sign-On Errors | resolved | minor | 50 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 Ninety with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"ninety"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}