Miro incident: Potential Service Disruptions (External Incident)

1. resolvedOct 20, 2025, 11:01 UTC

   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.

2. monitoringOct 20, 2025, 08:49 UTC

   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.

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.

• Vimeo: AI and Create services unavailableCritical · Oct 20, 2025, 07:55 UTC
• Convex: Many Convex backends are downMajor · Oct 20, 2025, 07:22 UTC
• Airtable: Airtable is partially unavailableMajor · Oct 20, 2025, 07:25 UTC
• 1Password: Intermittent performance issues with 1Password.comMajor · Oct 20, 2025, 09:05 UTC
• GitBook: Public content not loading or taking longer to loadMajor · Oct 20, 2025, 09:16 UTC
• Mux: Mux Player embeds increased error ratesMajor · Oct 20, 2025, 09:39 UTC
• Cloudinary: Degraded Performance in US DatacenterMinor · Oct 20, 2025, 07:51 UTC
• Pusher: MT1 cluster - increased latency and webhook delivery failuresMinor · Oct 20, 2025, 08:10 UTC
• New Relic: Data Irregularities - US and EU regionMinor · Oct 20, 2025, 08:40 UTC
• npm: Degraded performance of package publish and installMinor · Oct 20, 2025, 09:31 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