Miro outage: Miro is partially down

1. resolvedMay 4, 2026, 19:01 UTC

   The partial outage affecting Miro 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.

2. monitoringMay 4, 2026, 18:29 UTC

   We observe core access to Miro has been restored following the deployment of a fix for the primary issue. We're going to continue to monitor. Please reach out to our support team if there are any access issues.

3. identifiedMay 4, 2026, 18:21 UTC

   Core access to Miro has been restored following the deployment of a fix for the primary issue. Our team is now actively preparing a resolution for a secondary issue, which may cause some add-on functionalities to remain an issue. We will provide our next update within 30 minutes.

4. identifiedMay 4, 2026, 17:52 UTC

   We identified two issues causing the partial outage. We have addressed the first issue. Our team is continuing to investigate and preparing a fix for the second issue. We will confirm the status as updates occur.

5. identifiedMay 4, 2026, 17:15 UTC

   We have identified the cause of the ongoing partial outage, tracing it to a recent database connection update. Our team is actively working on a resolution to restore full service performance. Please note that this issue impacts all customers with EU data residency, irrespective of where users are physically located. Services for US and Australia data residency customers remain unaffected. We will provide our next update within 30 minutes.

6. investigatingMay 4, 2026, 16:23 UTC

   We are currently investigating reports of Miro not being fully accessible. Users may experience slower response times or delays when accessing the Application. 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Miro's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• 1Password: SaaS Manager workflows and integrations are failingCritical · May 4, 2026, 17:59 UTC
• Contentful: Some customers are experiencing issues logging inMajor · May 4, 2026, 13:20 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: (Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]Minor · May 1, 2026, 17:51 UTC

How often does Miro have incidents?

Miro reported 2 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 10h 14m. See Miro's uptime and incident history