- 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 56m it lasted.
Anything that failed between 2025-12-23 05:37 UTC and 2025-12-23 10:33 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 our Billing system affecting _account upgrades and reactivations, as well as starting trials._ Users may experience slower response times and errors when accessing the _Billing Upgrade pages_. Our engineering team is working to identify the root cause and will provide updates as we learn more. We apologize for any inconvenience this may cause and appreciate your patience.
provider
- monitoring
We have implemented a fix and waiting for it to propagate to all relevant endpoints. Our teams are continuing to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further issues are detected.
provider
- monitoring
We have rolled out a fix to the affected systems and are seeing some improvement, but we are continuing to monitor the situation closely. We are aiming to fully restore performance shortly.
provider
- resolved
The issue affecting certain upgrade/trial start scenarios 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-a35ae39826
Is Miro still down?
No, this incident was resolved 2025-12-23 10:33 UTC. For Miro's live state, see https://down.guide/miro.
How long did it last?
4h 56m, from 2025-12-23 05:37 UTC to 2025-12-23 10:33 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.