- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 37of 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 1h it lasted.
Anything that failed between 2025-10-30 10:11 UTC and 2025-10-30 11:11 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 3
- identified
We identified the cause of the _Performance Degradation in the US data residency_. We are actively working on a fix to restore normal performance. We will keep the status page updated.
provider
- monitoring
We have resolved the root cause of the performance degradation in the US data residency and we are actively monitoring the system to ensure proper functionality.
provider
- resolved
Everything is operational again. Thank you for your patience!
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-96b781f61b
Is Miro still down?
No, this incident was resolved 2025-10-30 11:11 UTC. For Miro's live state, see https://down.guide/miro.
How long did it last?
1h, from 2025-10-30 10:11 UTC to 2025-10-30 11:11 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.