- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 35of 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 24m it lasted.
Anything that failed between 2026-04-28 15:14 UTC and 2026-04-28 15:38 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 2
- monitoring
Between 15:40 CEST and 16:34 CEST on April 28, 2026, Sidekicks, diagram creation, and other AI moderation-dependent functionality were affected due to elevated error rates in our content moderation service. The issue has been resolved, and all systems are now operating normally. We apologize for the inconvenience caused.
provider
- resolved
Following 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 inconvenience caused.
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-927c1f2e29
Is Miro still down?
No, this incident was resolved 2026-04-28 15:38 UTC. For Miro's live state, see https://down.guide/miro.
How long did it last?
24m, from 2026-04-28 15:14 UTC to 2026-04-28 15:38 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.