Mode status history
Current state: operational — “All Systems Operational” per https://status.modeanalytics.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Mode incidents last?
From 13 incidents with a vendor-posted start and resolve time. Longest on record: Discovery Database Sync Delay — 46.1 h (2026-03-09 15:38 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 (13)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-27 09:00 UTC | Third Party Service Provider Interruption | resolved | major | 0 min |
| 2026-07-24 11:00 UTC | Service Timeout Error | resolved | none | 0 min |
| 2026-06-08 16:30 UTC | Microsoft SSO Authentication Errors | resolved | minor | 3 h 30 min |
| 2026-03-09 15:38 UTC | Discovery Database Sync Delay | resolved | minor | 46 h 08 min |
| 2026-01-09 21:01 UTC | Intercom outage affecting the in-app messenger | resolved | critical | 17 min |
| 2026-01-05 14:22 UTC | Intercom Outage | resolved | major | 47 min |
| 2025-12-18 17:02 UTC | Discovery Database Sync Delay | resolved | minor | 20 h 03 min |
| 2025-12-11 05:00 UTC | Resolved - Missing Notebook Visuals in Reports | resolved | none | 0 min |
| 2025-11-18 21:47 UTC | GitHub incident impacting Git Syncs | resolved | major | 27 min |
| 2025-11-18 09:00 UTC | Scheduled Report Failures | resolved | none | 4 h 00 min |
| 2025-11-06 13:54 UTC | Reports using Notebook generated Datasets failing to load | resolved | minor | 2 h 26 min |
| 2025-10-20 12:32 UTC | AWS outage impacting Mode - elevated errors and delays | resolved | minor | 23 h 35 min |
| 2025-10-20 12:21 UTC | Intercom Outage | resolved | major | 23 h 42 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 Mode with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"mode"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}