- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 25of 100
What to do
Check whether you use Miro in us. 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 23m it lasted.
Anything that failed between 2025-12-16 15:57 UTC and 2025-12-16 16:20 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
We have identified a degradation in our services. The problem has been solved and functionality 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.
provider
- resolved
The 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.
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-3d984d5e1f
Is Miro still down?
No, this incident was resolved 2025-12-16 16:20 UTC. For Miro's live state, see https://down.guide/miro.
How long did it last?
23m, from 2025-12-16 15:57 UTC to 2025-12-16 16:20 UTC, by the times Miro posted.
What was affected?
Miro named in us.
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.