Miro reported this major-impact incident on its official status page on Jan 22, 2026, 17:31 UTC. It was resolved after 4h 43m.
Right now Miro is operational. Live Miro status →
The _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 support team.
We are continuing to work on resolving the issue. _We are monitoring the process and_ aiming to fully restore performance shortly.
We identified the cause of the _increased error rates for Content Explorer and other parts of Admin console for Enterprise Guard users_. The issue is related to _a database issue._ We are actively working on a fix to restore normal performance. We will provide further updates as they are available_._
We are currently investigating reports of _Errors_ affecting _Enterprise Guard users_. Users may experience increased error rates in the Admin Console, while try to work with Content Explorer. Our engineering team has already identified the root cause working to mitigate the issue. We apologize for any inconvenience this may cause and appreciate your patience.
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.
Overlapping incidents aren't necessarily related.
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