Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    История сбоев Miro

    27 Miro incidents · апрель 2025 г. — official updates, affected components, duration and resolution details.

    Вернуться к текущему статусу

    Вход с именем пользователя и паролем недоступен

    Начало 8 сентября 2026 г. в 19:21 UTC · 19h 3m

    OutageСерьёзный инцидент
    1. 8 сентября 2026 г. в 19:21 UTCinvestigating

      Вход с паролем в настоящее время недоступен. Пожалуйста, подпишитесь Логин через SSO и социальный логин не затронут

    2. 9 сентября 2026 г. в 14:24 UTCresolved

      Проблема, затрагивающая вход в систему, теперь решена путем удаления возможности входа с паролем. Если вы продолжаете испытывать какие-либо проблемы, пожалуйста, обратитесь к нашей команде поддержки

    Автоматический перевод официального обновления инцидента.

    Периодические проблемы с регистрацией и входом пользователя

    Начало 31 августа 2026 г. в 14:31 UTC · 1h 26m

    OutageСерьёзный инцидент
    1. 31 августа 2026 г. в 14:31 UTCidentified

      В настоящее время мы идентифицируем проблему, затрагивающую небольшой процент пользователей, пытающихся войти или зарегистрироваться. Некоторые пользователи могут столкнуться с ошибкой при попытке зарегистрироваться или войти в Miro. Обработка: Если вы столкнулись с ошибкой при регистрации, пожалуйста, обновите страницу и попробуйте снова. Последующая попытка должна быть успешной. Наша инженерная команда активно изучает первопричину, и в ближайшее время мы предоставим еще одно обновление. Мы приносим извинения за любые неудобства, которые это может вызвать.

    2. 31 августа 2026 г. в 15:39 UTCmonitoring

      Мы успешно внедрили исправление и внимательно следили за результатами. Мы можем подтвердить, что процессы регистрации пользователей и входа в систему полностью восстановлены и функционируют нормально. Спасибо за ваше терпение, пока мы работали над решением этой проблемы.

    3. 31 августа 2026 г. в 15:57 UTCresolved

      Проблема, затрагивающая регистрацию пользователей и логины, решена. Возобновились обычные системные операции.

    Автоматический перевод официального обновления инцидента.

    Functionality degradation in Miro AI

    Начало 21 мая 2026 г. в 15:14 UTC · 3h 42m

    IssuesНезначительный инцидент
    1. 21 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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.

    Miro is partially down

    Начало 4 мая 2026 г. в 16:23 UTC · 2h 37m

    OutageСерьёзный инцидент
    1. 4 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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.

    Some users experienced issues with AI features

    Начало 28 апреля 2026 г. в 15:14 UTC · 24m

    OutageСерьёзный инцидент
    1. 28 апреля 2026 г. в 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 апреля 2026 г. в 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.

    Board access issue

    Начало 12 марта 2026 г. в 16:40 UTC · 3h 9m

    IssuesНезначительный инцидент
    1. 12 марта 2026 г. в 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 марта 2026 г. в 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 марта 2026 г. в 19:49 UTCresolved

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

    Issue affecting our service performance

    Начало 4 марта 2026 г. в 17:14 UTC · 27m

    IssuesНезначительный инцидент
    1. 4 марта 2026 г. в 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 марта 2026 г. в 17:24 UTCmonitoring

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

    3. 4 марта 2026 г. в 17:39 UTCmonitoring

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

    4. 4 марта 2026 г. в 17:41 UTCresolved

      Issue is resolved.

    MCP server performance degraded

    Начало 26 февраля 2026 г. в 13:27 UTC · 9m

    IssuesНезначительный инцидент
    1. 26 февраля 2026 г. в 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 февраля 2026 г. в 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.

    Calls to Public API and MCP server are failing

    Начало 13 февраля 2026 г. в 12:49 UTC · 2h 55m

    IssuesНезначительный инцидент
    1. 13 февраля 2026 г. в 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 февраля 2026 г. в 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 февраля 2026 г. в 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 февраля 2026 г. в 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 февраля 2026 г. в 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 февраля 2026 г. в 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.

    Enterprise Guard Admin Console issues

    Начало 22 января 2026 г. в 17:31 UTC · 4h 43m

    OutageСерьёзный инцидент
    1. 22 января 2026 г. в 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 января 2026 г. в 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 января 2026 г. в 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 января 2026 г. в 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.

    Inability to upgrade/reactivate accounts from free/startup tier and start trials

    Начало 23 декабря 2025 г. в 05:37 UTC · 4h 56m

    OutageСерьёзный инцидент
    1. 23 декабря 2025 г. в 05: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 декабря 2025 г. в 06: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 декабря 2025 г. в 08: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 декабря 2025 г. в 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.

    Degraded service in US region

    Начало 16 декабря 2025 г. в 15:57 UTC · 23m

    IssuesНезначительный инцидент
    1. 16 декабря 2025 г. в 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 декабря 2025 г. в 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.

    Ongoing incident with one of our providers - Cloudflare

    Начало 18 ноября 2025 г. в 14:11 UTC · 3h 19m

    IssuesНезначительный инцидент
    1. 18 ноября 2025 г. в 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 ноября 2025 г. в 17:30 UTCresolved

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

    Application degradation in the US data residency

    Начало 30 октября 2025 г. в 10:11 UTC · 1h 0m

    OutageСерьёзный инцидент
    1. 30 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 11:11 UTCresolved

      Everything is operational again. Thank you for your patience!

    Miro degraded

    Начало 20 октября 2025 г. в 19:41 UTC · 4h 48m

    OutageСерьёзный инцидент
    1. 20 октября 2025 г. в 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 октября 2025 г. в 22:03 UTCidentified

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

    3. 20 октября 2025 г. в 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 октября 2025 г. в 00: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 октября 2025 г. в 00: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.

    User search degradation

    Начало 20 октября 2025 г. в 17:47 UTC · 21h 43m

    OutageСерьёзный инцидент
    1. 20 октября 2025 г. в 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 октября 2025 г. в 00: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 октября 2025 г. в 09: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 октября 2025 г. в 09: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 октября 2025 г. в 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.

    Potential Service Disruptions (External Incident)

    Начало 20 октября 2025 г. в 08:49 UTC · 2h 11m

    IssuesНезначительный инцидент
    1. 20 октября 2025 г. в 08: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 октября 2025 г. в 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.

    Issue with creating support requests for customers with language set to Japanese

    Начало 10 сентября 2025 г. в 06:34 UTC · 30m

    IssuesНезначительный инцидент
    1. 10 сентября 2025 г. в 06: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 сентября 2025 г. в 06: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 сентября 2025 г. в 07: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.

    Issues with Tables and Timelines in EU region

    Начало 19 августа 2025 г. в 08:44 UTC · 53m

    Pending
    1. 19 августа 2025 г. в 08: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 августа 2025 г. в 09: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 августа 2025 г. в 09: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.

    PDF Export Functionality Degraded

    Начало 27 июня 2025 г. в 15:04 UTC · 15m

    Pending
    1. 27 июня 2025 г. в 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 июня 2025 г. в 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.