Historial de interrupciones de Miro

1. 8 de septiembre de 2026 a las 19:21 UTCinvestigating

   Iniciar sesión con contraseña es actualmente indisponible. Por favor, ingrese con Iniciar sesión a través de SSO y acceso social no es afectado

2. 9 de septiembre de 2026 a las 14:24 UTCresolved

   La cuestión que afecta al inicio de sesión ya se ha resuelto eliminando la opción de iniciar sesión con contraseña. Si sigues experimentando algún problema, por favor contacta con nuestro equipo de apoyo

Traducido automáticamente desde la actualización oficial del incidente.

1. 31 de agosto de 2026 a las 14:31 UTCidentified

   Actualmente estamos identificando un problema que afecta a un pequeño porcentaje de usuarios que intentan iniciar sesión o registrarse. Algunos usuarios pueden encontrar un error al intentar registrarse o registrarse en Miro. Medida de trabajo: Si encuentra un error durante el registro, por favor, refresque la página e inténtelo de nuevo. Un intento ulterior debería tener éxito. Nuestro equipo de ingeniería está investigando activamente la causa raíz, y proporcionaremos otra actualización en breve. Nos disculpamos por cualquier inconveniente que esto pueda causar.

2. 31 de agosto de 2026 a las 15:39 UTCmonitoring

   Hemos implementado con éxito una corrección y monitoreado de cerca los resultados. Podemos confirmar que el registro de usuario y los procesos de inicio de sesión están completamente recuperados y funcionan normalmente. Gracias por su paciencia mientras trabajamos para resolver este problema.

3. 31 de agosto de 2026 a las 15:57 UTCresolved

   Se ha resuelto la cuestión que afecta a las inscripciones y los logins de los usuarios. Se han reanudado las operaciones normales del sistema.

Traducido automáticamente desde la actualización oficial del incidente.

1. 21 de mayo de 2026 a las 15:14 UTCinvestigating

   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 more. We apologize for any inconvenience this may cause and appreciate your patience.

2. 21 de mayo de 2026 a las 17:27 UTCmonitoring

   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. 21 de mayo de 2026 a las 18:56 UTCresolved

   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.

1. 4 de mayo de 2026 a las 16:23 UTCinvestigating

   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.

2. 4 de mayo de 2026 a las 17:15 UTCidentified

   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.

3. 4 de mayo de 2026 a las 17:52 UTCidentified

   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. 4 de mayo de 2026 a las 18:21 UTCidentified

   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. 4 de mayo de 2026 a las 18:29 UTCmonitoring

   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. 4 de mayo de 2026 a las 19:01 UTCresolved

   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.

1. 28 de abril de 2026 a las 15:14 UTCmonitoring

   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. We apologize for the inconvenience caused.

2. 28 de abril de 2026 a las 15:38 UTCresolved

   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.

1. 12 de marzo de 2026 a las 16:40 UTCidentified

   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 disruption this may cause.

2. 12 de marzo de 2026 a las 19:40 UTCmonitoring

   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 issues are detected.

3. 12 de marzo de 2026 a las 19:49 UTCresolved

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

1. 4 de marzo de 2026 a las 17:14 UTCinvestigating

   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.

2. 4 de marzo de 2026 a las 17:24 UTCmonitoring

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

3. 4 de marzo de 2026 a las 17:39 UTCmonitoring

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

4. 4 de marzo de 2026 a las 17:41 UTCresolved

   Issue is resolved.

1. 26 de febrero de 2026 a las 13:27 UTCinvestigating

   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.

2. 26 de febrero de 2026 a las 13:36 UTCresolved

   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.

1. 13 de febrero de 2026 a las 12:49 UTCidentified

   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. 13 de febrero de 2026 a las 13:20 UTCidentified

   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. 13 de febrero de 2026 a las 13:31 UTCmonitoring

   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. 13 de febrero de 2026 a las 13:59 UTCmonitoring

   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. 13 de febrero de 2026 a las 14:22 UTCmonitoring

   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. 13 de febrero de 2026 a las 15:45 UTCresolved

   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.

1. 22 de enero de 2026 a las 17:31 UTCinvestigating

   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 issue. We apologize for any inconvenience this may cause and appreciate your patience.

2. 22 de enero de 2026 a las 17:36 UTCidentified

   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 they are available_._

3. 22 de enero de 2026 a las 20:36 UTCidentified

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

4. 22 de enero de 2026 a las 22:13 UTCresolved

   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.

1. 23 de diciembre de 2025 a las 5:37 UTCinvestigating

   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 the root cause and will provide updates as we learn more. We apologize for any inconvenience this may cause and appreciate your patience.

2. 23 de diciembre de 2025 a las 6:41 UTCmonitoring

   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. 23 de diciembre de 2025 a las 8:07 UTCmonitoring

   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. 23 de diciembre de 2025 a las 10:33 UTCresolved

   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.

1. 16 de diciembre de 2025 a las 15:57 UTCmonitoring

   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. 16 de diciembre de 2025 a las 16:20 UTCresolved

   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.

1. 18 de noviembre de 2025 a las 14:11 UTCmonitoring

   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. 18 de noviembre de 2025 a las 17:30 UTCresolved

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

1. 30 de octubre de 2025 a las 10:11 UTCidentified

   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. 30 de octubre de 2025 a las 10:57 UTCmonitoring

   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. 30 de octubre de 2025 a las 11:11 UTCresolved

   Everything is operational again. Thank you for your patience!

1. 20 de octubre de 2025 a las 19:41 UTCidentified

   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. 20 de octubre de 2025 a las 22:03 UTCidentified

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

3. 20 de octubre de 2025 a las 23:55 UTCidentified

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

4. 21 de octubre de 2025 a las 0:06 UTCmonitoring

   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.

5. 21 de octubre de 2025 a las 0:29 UTCresolved

   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.

1. 20 de octubre de 2025 a las 17:47 UTCinvestigating

   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 more. We apologize for any inconvenience this may cause and appreciate your patience.

2. 21 de octubre de 2025 a las 0:34 UTCidentified

   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. 21 de octubre de 2025 a las 9:06 UTCidentified

   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. 21 de octubre de 2025 a las 9:32 UTCidentified

   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. 21 de octubre de 2025 a las 15:30 UTCresolved

   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 our support team.

1. 20 de octubre de 2025 a las 8:49 UTCmonitoring

   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. 20 de octubre de 2025 a las 11:01 UTCresolved

   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.

1. 10 de septiembre de 2025 a las 6:34 UTCinvestigating

   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 the root cause and will provide updates as we learn more. We apologize for any inconvenience this may cause and appreciate your patience.

2. 10 de septiembre de 2025 a las 6:44 UTCidentified

   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. 10 de septiembre de 2025 a las 7:04 UTCresolved

   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.

1. 19 de agosto de 2025 a las 8:44 UTCidentified

   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. 19 de agosto de 2025 a las 9:09 UTCmonitoring

   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. 19 de agosto de 2025 a las 9:37 UTCresolved

   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.

1. 27 de junio de 2025 a las 15:04 UTCidentified

   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. 27 de junio de 2025 a las 15:19 UTCresolved

   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.