- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 29of 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 2h 11m it lasted.
Anything that failed between 2025-10-20 08:49 UTC and 2025-10-20 11:01 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’re aware of widespread external issues that may be affecting some third-party integrations with Miro. While Miro itself is fully operational, certain features may experience temporary disruptions until these external issues are resolved.
provider
- resolved
Earlier disruptions were due to a significant Amazon Web Services outage. While AWS is completing their remediation, the majority of their services are now operational and we have observed recovery in multiple third-party systems.
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-4daa5d6f4e
Is Miro still down?
No, this incident was resolved 2025-10-20 11:01 UTC. For Miro's live state, see https://down.guide/miro.
How long did it last?
2h 11m, from 2025-10-20 08:49 UTC to 2025-10-20 11:01 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.