Miro

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-08 19:21 UTC

   Sign in with password is currently unavailable. Please sign in with Login via SSO and social login is unaffected

2. resolved 2026-09-09 14:24 UTC

   The issue affecting sign-in has now been resolved by removing the option to login with password. If you continue to experience any issues, please reach out to our support team

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-31 14:31 UTC

   We are currently identifying an issue affecting a small percentage of users attempting to log in or register. Some users may encounter an error when trying to sign up or sign in to Miro. Workaround: If you encounter an error during registration, please refresh the page and try...

2. monitoring 2026-08-31 15:39 UTC

   We have successfully implemented a fix and closely monitored the results. We can confirm that user registration and login processes are fully recovered and functioning normally. Thank you for your patience while we worked to resolve this issue.

3. resolved 2026-08-31 15:57 UTC

   The issue affecting user registrations and logins has been resolved. Normal system operations have resumed.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-21 15:14 UTC

   We are currently investigating reports of functionality degradation affecting Miro AI. Users may experience slower response times, delays or unavailability when accessing Miro AI. Our engineering team is working to identify the root cause and will provide updates as we learn...

2. monitoring 2026-05-21 17:27 UTC

   We have implemented a fix. Miro AI availability has returned to normal levels. Our team will continue to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further issues are detected.

3. resolved 2026-05-21 18:56 UTC

   The issue affecting Miro AI 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-04 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...

2. identified 2026-05-04 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...

3. identified 2026-05-04 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.

4. identified 2026-05-04 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.

5. monitoring 2026-05-04 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.

6. resolved 2026-05-04 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-04-28 15:14 UTC

   Between 15:40 CEST and 16:34 CEST on April 28, 2026, Sidekicks, diagram creation, and other AI moderation-dependent functionality were affected due to elevated error rates in our content moderation service. The issue has been resolved, and all systems are now operating normally....

2. resolved 2026-04-28 15:38 UTC

   Following continued monitoring after mitigation was applied, we can confirm that the issue has been fully resolved and all affected AI-powered functionality is operating normally. We apologize again for the inconvenience caused.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-12 16:40 UTC

   We are currently fixing an issue affecting board access in our platform. Some users may experience difficulties opening or accessing their boards. Our team is actively working on a resolution and we will provide updates as soon as we have more information. We apologize for any...

2. monitoring 2026-03-12 19:40 UTC

   We have implemented a fix for the boards not opening issue (Only boards with sticky stacks were affected). Functionality should be returning to normal. Our team will continue to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further...

3. resolved 2026-03-12 19:49 UTC

   Incident was resolved. Thank you for your patience. Board functionality is back to normal.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-04 17:14 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....

2. monitoring 2026-03-04 17:24 UTC

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

3. monitoring 2026-03-04 17:39 UTC

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

4. resolved 2026-03-04 17:41 UTC

   Issue is resolved.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-26 13:27 UTC

   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...

2. resolved 2026-02-26 13:36 UTC

   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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-13 12:49 UTC

   We identified the cause of the failing requests to our Public API. This includes requests to Miro MCP services. We are actively working on a fix to restore normal performance. We will provide further updates in _30 minutes._

2. identified 2026-02-13 13:20 UTC

   We are continuing to work on resolving the issue for Public API and MCP server. We are applying and rolling out a fix to the affected systems. We are aiming to fully restore performance as soon as possible.

3. monitoring 2026-02-13 13:31 UTC

   We have implemented a fix. Public API and MCP server error rates have returned to normal levels. Our team will continue to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further issues are detected.

4. monitoring 2026-02-13 13:59 UTC

   Some users had trouble _with_ Public API and MCP server in US and AU as well. We have implemented a fix for this issue and our team will continue to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further issues are detected.

5. monitoring 2026-02-13 14:22 UTC

   We have implemented a fix. Errors has returned to normal levels. Our team will continue to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further issues are detected.

6. resolved 2026-02-13 15:45 UTC

   The performance degradation affecting Public API and 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-22 17:31 UTC

   We are currently investigating reports of _Errors_ affecting _Enterprise Guard users_. Users may experience increased error rates in the Admin Console, while try to work with Content Explorer. Our engineering team has already identified the root cause working to mitigate the...

2. identified 2026-01-22 17:36 UTC

   We identified the cause of the _increased error rates for Content Explorer and other parts of Admin console for Enterprise Guard users_. The issue is related to _a database issue._ We are actively working on a fix to restore normal performance. We will provide further updates as...

3. identified 2026-01-22 20:36 UTC

   We are continuing to work on resolving the issue. _We are monitoring the process and_ aiming to fully restore performance shortly.

4. resolved 2026-01-22 22:13 UTC

   The _issue_ affecting Enterprise Guard customers 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-23 05:37 UTC

   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...

2. monitoring 2025-12-23 06:41 UTC

   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.

3. monitoring 2025-12-23 08:07 UTC

   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.

4. resolved 2025-12-23 10:33 UTC

   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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-12-16 15:57 UTC

   We have identified a degradation in our services. The problem has been solved and functionality has returned to normal levels. Our team will continue to monitor the systems closely to ensure stability. We will confirm the resolution shortly if no further issues are detected.

2. resolved 2025-12-16 16:20 UTC

   The degradation affecting our services 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. monitoring 2025-11-18 14:11 UTC

   Due to an ongoing incident with one of our providers - Cloudflare (see status [here](https://www.cloudflarestatus.com/)) Miro is experiencing degradation of certain features like Prototypes and Slides. We are monitoring the situation and will provide continuous updates.

2. resolved 2025-11-18 17:30 UTC

   Our services have returned to normal. We will continue to monitor the Cloudflare updates and change the status accordingly if needed.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-10-30 10:11 UTC

   We identified the cause of the _Performance Degradation in the US data residency_. We are actively working on a fix to restore normal performance. We will keep the status page updated.

2. monitoring 2025-10-30 10:57 UTC

   We have resolved the root cause of the performance degradation in the US data residency and we are actively monitoring the system to ensure proper functionality.

3. resolved 2025-10-30 11:11 UTC

   Everything is operational again. Thank you for your patience!

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-10-20 19:41 UTC

   We are aware of degradation affecting core Miro functionality. Users may experience slower response times or errors. Our engineering team has identified the issue and is working on a fix. We apologize for any inconvenience this may cause and appreciate your patience.

2. identified 2025-10-20 21:07 UTC

   Our engineering team continue to work toward restoring service. We apologize again for any inconvenience caused.

3. identified 2025-10-20 22:03 UTC

   Our engineering team continue to work toward restoring service. We apologize again for any inconvenience caused.

4. identified 2025-10-20 22:44 UTC

   Our engineering team continues to work towards restoring service. We will be updating this status every 30 minutes or until service is restored.

5. identified 2025-10-20 23:16 UTC

   Our engineering team continues to work towards restoring service. We will be updating this status every 30 minutes or until service is restored.

6. identified 2025-10-20 23:55 UTC

   Our engineering team continues to work towards restoring service. We will be updating this status every 30 minutes or until service is restored.

7. monitoring 2025-10-21 00:06 UTC

   We have implemented a fix and service has returned to normal levels. Our team will continue to monitor systems closely to ensure stability. We will confirm the resolution if no further issues are detected.

8. resolved 2025-10-21 00:29 UTC

   The issue affecting core Miro functionality has now 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-20 17:47 UTC

   We're currently investigating reports of a degradation in user search. This is impacting the ability to share boards, tag in comments and various other user-related functionality. Our engineering team is working to identify the root cause and will provide updates as we learn...

2. identified 2025-10-21 00:34 UTC

   We have identified the cause of the degradation in user search and are gradually rolling out a fix across all of our enterprise customers. We appreciate your ongoing patience.

3. identified 2025-10-21 09:06 UTC

   We’re continuing the gradual rollout of the fix for the user search degradation. Many enterprise customers should already see recovery, with full resolution expected once the rollout completes.

4. identified 2025-10-21 09:32 UTC

   We have completed the rollout of the fix for the user search degradation to enterprise customers with US and Australia data residency. We continue the gradual rollout of the fix to customers in the EU region.

5. resolved 2025-10-21 15:30 UTC

   Following the completion of the rollout of a fix to all enterprise customers, the degradation affecting user search 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...

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2025-10-20 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.

2. resolved 2025-10-20 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-10 06:34 UTC

   Customers with language set to Japanese are unable to raise support requests via the learning centre or access learning centre content. While we are investigating - it is still possible to contact support by using the following link: Our engineering team is working to identify...

2. identified 2025-09-10 06:44 UTC

   We identified the cause of the issue which is affecting users using Miro in the Japanese and Portuguese languages. The issue is related to a software update that we are now fixing. We will provide further updates in 15 minutes.

3. resolved 2025-09-10 07:04 UTC

   The Learning centre issue affecting users in Japanese and Portuguese languages has now 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-08-19 08:44 UTC

   We identified the issue with Tables and Timelines that our customers may experience in EU region. We are actively investigating the issue and working on restoring normal performance. We will provide further updates when the fix is rolled out.

2. monitoring 2025-08-19 09:09 UTC

   We have rolled out the fix. Tables and Timelines performance has returned to normal levels. Our team will continue to monitor the systems closely to ensure stability.

3. resolved 2025-08-19 09:37 UTC

   The issue affecting Tables and Timelines 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-06-27 15:04 UTC

   Our team has identified and is working to resolve an issue that is preventing users from exporting boards, frames, or widgets as high-quality PDF files. We apologize for the inconvenience and appreciate your patience. We’ll share updates as soon as more information is available.

2. resolved 2025-06-27 15:19 UTC

   The issue affecting PDF export functionality 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-26 10:34 UTC

   We are investigating a degraded performance of the Images and Icons tool. Icons supplied via this tool may not appear in search results, attempts to save these icons may fail. We’re working with the provider to resolve the issue and will provide updates as they become available.

2. identified 2025-06-27 06:14 UTC

   We’ve identified the root cause of the issue affecting icons in the Images and Icons tool and are working closely with our partner to restore full functionality. Icons may still be missing from search results or fail to save during this time. We apologize for the inconvenience...

3. resolved 2025-06-27 11:28 UTC

   The issue affecting icons in the Images and Icons tool has now 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-23 06:05 UTC

   We are currently investigating reports of users not receiving emails allowing them to login when they first register. 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...

2. identified 2025-06-23 06:55 UTC

   We identified the cause of the sign-in issue. The issue is related to new accounts only. We are actively working on a fix to restore normal performance. We will provide further updates in 30 minutes.

3. monitoring 2025-06-23 07:26 UTC

   We have implemented a fix. Our team will continue to monitor the systems closely to ensure stability. We advise users to try again if they did not receive a sign in email

4. resolved 2025-06-23 08:56 UTC

   The issue affecting sign in for new accounts 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-26 09:32 UTC

   We are currently investigating issues affecting opening and using Blueprint templates. 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.

2. identified 2025-05-26 09:40 UTC

   We identified the cause of the issue with the Blueprints. We are actively working on a fix to restore normal performance

3. resolved 2025-05-26 10:06 UTC

   The issue affecting using Blueprints has been partially resolved. It is possible to create a Blueprint using the Preview option. We apologize for the inconvenience caused and appreciate your understanding

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-05-19 11:35 UTC

   We’ve identified an issue affecting some users on the Enterprise plan where team invitations are successfully created and processed, but the invitation email is not delivered to the invitee. We’ve identified the root cause and are working on a fix.

2. resolved 2025-05-19 14:13 UTC

   The issue that was preventing team invitation emails from being delivered correctly 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.

Excerpts are shortened. Read the full incident on Miro's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-19 10:05 UTC

   We’re currently investigating a degradation in image upload functionality within AI features. This is impacting related features like image generation and alteration, which may not work reliably. We’ll share updates as we learn more.

2. identified 2025-05-19 11:29 UTC

   We've identified the root cause of the image upload issues affecting AI features and are working on a fix.

3. resolved 2025-05-19 14:16 UTC

   The issue causing degraded image upload functionality within AI features 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.

Excerpts are shortened. Read the full incident on Miro's status page.