Miro Outage History

16 incidents recorded over the last 365 days, 16 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Miro status100.00% uptime history

Every Recorded Miro Incident

Miro incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
May 21, 2026AU » Functionality degradation in Miro AI1780h 42mResolved
May 4, 2026EU » Miro is partially down2187h 33mResolved
Apr 28, 2026Some users experienced issues with AI features20 minResolved
Mar 12, 2026Board access issue3h 8mResolved
Mar 4, 2026Issue affecting our service performance26 minResolved
Feb 26, 2026MCP server performance degraded8 minResolved
Feb 13, 2026Calls to Public API and MCP server are failing2h 55mResolved
Jan 22, 2026Enterprise Guard Admin Console issues4h 42mResolved
Dec 23, 2025Inability to upgrade/reactivate accounts from free/startup tier and start trials4h 56mResolved
Dec 16, 2025Degraded service in US region22 minResolved
Nov 18, 2025Ongoing incident with one of our providers - Cloudflare3h 19mResolved
Oct 30, 2025Application degradation in the US data residency1h 0mResolved
Oct 20, 2025Miro degraded4h 48mResolved
Oct 20, 2025User search degradation21h 43mResolved
Oct 20, 2025Potential Service Disruptions (External Incident)2h 11mResolved
Sep 10, 2025Issue with creating support requests for customers with language set to Japanese29 minResolved

How to Read This Miro Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Miro acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Miro outage in this window ran 91d 3h, against a mean recovery of 10d 11h. If you depend on Miro in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.