Vendor Status Watch

← all vendors

Miro status history

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

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

How long do Miro incidents last?

2.6 hmedian incident duration19 measured
4.9 h90th percentile1 in 10 ran longer
4.7 hmedian, major/critical only9 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-08 19:21 UTCSign-in with username and password is unavailableresolvedmajor19 h 02 min
2026-08-31 14:31 UTCIntermittent Issues with User Registration and Loginresolvedmajor1 h 25 min
2026-05-21 15:14 UTCFunctionality degradation in Miro AIresolvedminor3 h 41 min
2026-05-04 16:23 UTCMiro is partially downresolvedmajor2 h 37 min
2026-04-28 15:14 UTCSome users experienced issues with AI featuresresolvedmajor23 min
2026-03-12 16:40 UTCBoard access issueresolvedminor3 h 08 min
2026-03-04 17:14 UTCIssue affecting our service performanceresolvedminor26 min
2026-02-26 13:27 UTCMCP server performance degradedresolvedminor8 min
2026-02-13 12:49 UTCCalls to Public API and MCP server are failingresolvedminor2 h 55 min
2026-01-22 17:31 UTCEnterprise Guard Admin Console issuesresolvedmajor4 h 42 min
2025-12-23 05:37 UTCInability to upgrade/reactivate accounts from free/startup tier and start trialsresolvedmajor4 h 56 min
2025-12-16 15:57 UTCDegraded service in US regionresolvedminor22 min
2025-11-18 14:11 UTCOngoing incident with one of our providers - Cloudflareresolvedminor3 h 19 min
2025-10-30 10:11 UTCApplication degradation in the US data residencyresolvedmajor1 h 00 min
2025-10-20 19:41 UTCMiro degradedresolvedmajor4 h 48 min
2025-10-20 17:47 UTCUser search degradationresolvedmajor21 h 43 min
2025-10-20 08:49 UTCPotential Service Disruptions (External Incident)resolvedminor2 h 11 min
2025-09-10 06:34 UTCIssue with creating support requests for customers with language set to Japaneseresolvedminor29 min
2025-08-19 08:44 UTCIssues with Tables and Timelines in EU regionresolvednone52 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
}