Miro status history
Current state: operational — “All Systems Operational” per https://status.miro.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Miro incidents last?
From 19 incidents with a vendor-posted start and resolve time. Longest on record: User search degradation — 21.7 h (2025-10-20 17:47 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 (19)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-08 19:21 UTC | Sign-in with username and password is unavailable | resolved | major | 19 h 02 min |
| 2026-08-31 14:31 UTC | Intermittent Issues with User Registration and Login | resolved | major | 1 h 25 min |
| 2026-05-21 15:14 UTC | Functionality degradation in Miro AI | resolved | minor | 3 h 41 min |
| 2026-05-04 16:23 UTC | Miro is partially down | resolved | major | 2 h 37 min |
| 2026-04-28 15:14 UTC | Some users experienced issues with AI features | resolved | major | 23 min |
| 2026-03-12 16:40 UTC | Board access issue | resolved | minor | 3 h 08 min |
| 2026-03-04 17:14 UTC | Issue affecting our service performance | resolved | minor | 26 min |
| 2026-02-26 13:27 UTC | MCP server performance degraded | resolved | minor | 8 min |
| 2026-02-13 12:49 UTC | Calls to Public API and MCP server are failing | resolved | minor | 2 h 55 min |
| 2026-01-22 17:31 UTC | Enterprise Guard Admin Console issues | resolved | major | 4 h 42 min |
| 2025-12-23 05:37 UTC | Inability to upgrade/reactivate accounts from free/startup tier and start trials | resolved | major | 4 h 56 min |
| 2025-12-16 15:57 UTC | Degraded service in US region | resolved | minor | 22 min |
| 2025-11-18 14:11 UTC | Ongoing incident with one of our providers - Cloudflare | resolved | minor | 3 h 19 min |
| 2025-10-30 10:11 UTC | Application degradation in the US data residency | resolved | major | 1 h 00 min |
| 2025-10-20 19:41 UTC | Miro degraded | resolved | major | 4 h 48 min |
| 2025-10-20 17:47 UTC | User search degradation | resolved | major | 21 h 43 min |
| 2025-10-20 08:49 UTC | Potential Service Disruptions (External Incident) | resolved | minor | 2 h 11 min |
| 2025-09-10 06:34 UTC | Issue with creating support requests for customers with language set to Japanese | resolved | minor | 29 min |
| 2025-08-19 08:44 UTC | Issues with Tables and Timelines in EU region | resolved | none | 52 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 Miro with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"miro"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}