Issue affecting our service performance

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 27m it lasted.

  Anything that failed between 2026-03-04 17:14 UTC and 2026-03-04 17:41 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

1. investigatingMar 4, 2026, 5:14 PM UTC

   We are currently investigating an issue affecting our service. We identified elevated CPU utilization on our content database, which is causing performance degradation. Current Impact: Users may experience slow loading times or failures when attempting to open boards and spaces. What We're Doing: Our engineering team is actively investigating the root cause and exploring mitigation options to restore normal service performance. Next Steps: We will provide updates as we make progress toward resolution. We sincerely apologize for the disruption and appreciate your patience.

   provider

2. monitoringMar 4, 2026, 5:24 PM UTC

   Identified the issue and have mitigated the impact. We will continue monitoring and take more follow up actions.

   provider

3. monitoringMar 4, 2026, 5:39 PM UTC

   Performance should have returned to normal. We are still monitoring to ensure the experience is restored.

   provider

4. resolvedMar 4, 2026, 5:41 PM UTC

   Issue is resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.