Vendor Status Watch

← all vendors

Ninety status history

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

2incidents, last 30 days
3incidents, last 90 days
14incidents on record
Incidents per week, last 12 weeks:

How long do Ninety incidents last?

113 minmedian incident duration14 measured
20.4 h90th percentile1 in 10 ran longer
2.1 hmedian, major/critical only6 incidents

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)

StartedIncidentStatusImpactDuration
2026-08-27 15:40 UTCQuarterly and Annual 1:1s unable to loadresolvedminor23 min
2026-08-27 13:07 UTCQuarterly and Annual 1:1s having issuesresolvedminor4 min
2026-07-16 13:25 UTCSignups Currently Unavailableresolvedminor19 min
2026-06-12 18:25 UTCMicrosoft To-Do Integration: Service Degradedresolvedminor17 d 22 h
2026-05-21 17:01 UTCAccountability Chart - Some companies experiencing errorsresolvedmajor2 h 55 min
2026-05-11 18:07 UTCZapier Integration - Some users experiencing rate limitingresolvedmajor1 h 17 min
2026-01-12 15:26 UTCUsers Unable to Create Rocksresolvedmajor31 min
2025-12-03 14:26 UTCInviting users having issuesresolvedmajor3 h 48 min
2025-12-02 20:19 UTCSigning up and inviting new customers failingresolvedmajor5 h 50 min
2025-10-20 17:25 UTCLive Chat Support Latencyresolvedminor5 h 04 min
2025-10-20 16:35 UTCSome clients are experiencing latency or message failure issues with Mazresolvedminor20 h 25 min
2025-08-26 13:10 UTCLogin Failuresresolvedmajor50 min
2025-08-22 14:39 UTCusers logging in with eos.ninety.io experiencing issuesresolvedminor2 h 30 min
2025-08-18 14:22 UTCMicrosoft Single Sign-On Errorsresolvedminor50 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
}