- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 9m it lasted.
Anything that failed between 2026-02-26 13:27 UTC and 2026-02-26 13:36 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
- investigating
We are currently investigating reports of Performance Degradation affecting Miro _MCP server_. Users may experience slower response times or delays when accessing the _MCP._ 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
- resolved
The Performance Degradation affecting MCP server 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-11d478beb1
Is Miro still down?
No, this incident was resolved 2026-02-26 13:36 UTC. For Miro's live state, see https://down.guide/miro.
How long did it last?
9m, from 2026-02-26 13:27 UTC to 2026-02-26 13:36 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.