Miro reported this minor-impact incident on its official status page on Feb 13, 2026, 12:49 UTC. It was resolved after 2h 55m.
Right now Miro is operational. Live Miro status →
The 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 reach out to our support team.
We have implemented a fix. Errors has returned to normal levels. Our team will continue to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further issues are detected.
Some users had trouble _with_ Public API and MCP server in US and AU as well. We have implemented a fix for this issue and our team will continue to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further issues are detected.
We have implemented a fix. Public API and MCP server error rates have returned to normal levels. Our team will continue to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further issues are detected.
We are continuing to work on resolving the issue for Public API and MCP server. We are applying and rolling out a fix to the affected systems. We are aiming to fully restore performance as soon as possible.
We identified the cause of the failing requests to our Public API. This includes requests to Miro MCP services. We are actively working on a fix to restore normal performance. We will provide further updates in _30 minutes._
Our 5-minute checks didn't record a change in Miro's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Miro reported 2 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 10h 14m. See Miro's uptime and incident history