Miro Outage History

18 incidents recorded over the last 365 days, 18 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.

Every Recorded Miro Incident

Miro incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 3, 2026Scheduled Maintenance Notice3h 50mResolved
Sep 8, 2026Sign-in with username and password is unavailableThe issue affecting sign-in has now been resolved by removing the option to login with password.  If you continue to experience any issues, please reach out to our support team19h 2mResolved
Aug 31, 2026Intermittent Issues with User Registration and LoginThe issue affecting user registrations and logins has been resolved. Normal system operations have resumed.1h 25mResolved
May 21, 2026Functionality degradation in Miro AIThe issue affecting Miro AI has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our support team.3h 34mResolved
May 4, 2026Miro is partially downThe partial outage affecting Miro has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our support team.2h 30mResolved
Apr 28, 2026Some users experienced issues with AI featuresFollowing continued monitoring after mitigation was applied, we can confirm that the issue has been fully resolved and all affected AI-powered functionality is operating normally. We apologize again for the…20 minResolved
Mar 12, 2026Board access issueIncident was resolved. Thank you for your patience. Board functionality is back to normal.3h 8mResolved
Mar 4, 2026Issue affecting our service performanceIssue is resolved.26 minResolved
Feb 26, 2026MCP server performance degradedThe Performance Degradation affecting MCP server has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our…8 minResolved
Feb 13, 2026Calls to Public API and MCP server are failingThe performance degradation affecting Public API and MCP Server has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please…2h 55mResolved
Jan 22, 2026Enterprise Guard Admin Console issuesThe _issue_ affecting Enterprise Guard customers has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our…4h 42mResolved
Dec 23, 2025Inability to upgrade/reactivate accounts from free/startup tier and start trialsThe issue affecting certain upgrade/trial start scenarios has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out…4h 56mResolved
Dec 16, 2025Degraded service in US regionThe degradation affecting our services has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our support team.22 minResolved
Nov 18, 2025Ongoing incident with one of our providers - CloudflareOur services have returned to normal. We will continue to monitor the Cloudflare updates and change the status accordingly if needed.3h 19mResolved
Oct 30, 2025Application degradation in the US data residencyEverything is operational again. Thank you for your patience!1h 0mResolved
Oct 20, 2025Miro degradedThe issue affecting core Miro functionality has now been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our…4h 48mResolved
Oct 20, 2025User search degradationFollowing the completion of the rollout of a fix to all enterprise customers, the degradation affecting user search has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding…21h 43mResolved
Oct 20, 2025Potential Service Disruptions (External Incident)Earlier disruptions were due to a significant Amazon Web Services outage. While AWS is completing their remediation, the majority of their services are now operational and we have observed recovery in multiple…2h 11mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Miro incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

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 21h 43m, against a mean recovery of 4h 28m. 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.