- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 41of 100
What to do
Check whether your product depends on Miro. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 4h 43m it lasted.
Anything that failed between 2026-01-22 17:31 UTC and 2026-01-22 22:13 UTC may need a replay.Subscribe to Miro's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=miro works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Miro 4
- investigating
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.
provider
- identified
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_._
provider
- identified
We are continuing to work on resolving the issue. _We are monitoring the process and_ aiming to fully restore performance shortly.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-bcd00328d9
Is Miro still down?
No, this incident was resolved 2026-01-22 22:13 UTC. For Miro's live state, see https://down.guide/miro.
How long did it last?
4h 43m, from 2026-01-22 17:31 UTC to 2026-01-22 22:13 UTC, by the times Miro posted.
What caused it?
Miro hasn't published a root cause. If it does, it shows here.
Where does this come from?
Miro's official status page, https://status.miro.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.