Miro Outage History

Miro is up right now

There were 14 Miro outages since February 13, 2026 totaling 6h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.miro.com

Minor April 28, 2026

[AU] Some users experienced issues with AI features

Detected by Pingoru
Apr 28, 2026, 03:38 PM UTC
Resolved
Apr 28, 2026, 03:38 PM UTC
Duration
—
Affected: Application
Timeline · 2 updates
  1. monitoring Apr 28, 2026, 03:14 PM UTC

    Status: Monitoring 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. Affected components Application (Partial outage)

  2. resolved Apr 28, 2026, 03:38 PM UTC

    Status: Resolved 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. Affected components Application (Operational)

Read the full incident report →

Minor April 28, 2026

[EU] Some users experienced issues with AI features

Detected by Pingoru
Apr 28, 2026, 03:38 PM UTC
Resolved
Apr 28, 2026, 03:38 PM UTC
Duration
—
Affected: Application
Timeline · 2 updates
  1. monitoring Apr 28, 2026, 03:14 PM UTC

    Status: Monitoring 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. Affected components Application (Partial outage)

  2. resolved Apr 28, 2026, 03:38 PM UTC

    Status: Resolved 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. Affected components Application (Operational)

Read the full incident report →

Minor April 28, 2026

[US] Some users experienced issues with AI features

Detected by Pingoru
Apr 28, 2026, 03:38 PM UTC
Resolved
Apr 28, 2026, 03:38 PM UTC
Duration
—
Affected: Application
Timeline · 2 updates
  1. monitoring Apr 28, 2026, 03:14 PM UTC

    Status: Monitoring 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. Affected components Application (Partial outage)

  2. resolved Apr 28, 2026, 03:38 PM UTC

    Status: Resolved 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. Affected components Application (Operational)

Read the full incident report →

Minor March 12, 2026

[AU] Board access issue

Detected by Pingoru
Mar 12, 2026, 07:49 PM UTC
Resolved
Mar 12, 2026, 07:49 PM UTC
Duration
—
Affected: Application
Timeline · 3 updates
  1. identified Mar 12, 2026, 04:40 PM UTC

    Status: Identified 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. Affected components Application (Degraded performance)

  2. monitoring Mar 12, 2026, 07:40 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  3. resolved Mar 12, 2026, 07:49 PM UTC

    Status: Resolved Incident was resolved. Thank you for your patience. Board functionality is back to normal. Affected components Application (Operational)

Read the full incident report →

Minor March 12, 2026

[US] Board access issue

Detected by Pingoru
Mar 12, 2026, 07:49 PM UTC
Resolved
Mar 12, 2026, 07:49 PM UTC
Duration
—
Affected: Application
Timeline · 3 updates
  1. identified Mar 12, 2026, 04:40 PM UTC

    Status: Identified 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. Affected components Application (Degraded performance)

  2. monitoring Mar 12, 2026, 07:40 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  3. resolved Mar 12, 2026, 07:49 PM UTC

    Status: Resolved Incident was resolved. Thank you for your patience. Board functionality is back to normal. Affected components Application (Operational)

Read the full incident report →

Minor March 4, 2026

[EU] Issue affecting our service performance

Detected by Pingoru
Mar 04, 2026, 05:41 PM UTC
Resolved
Mar 04, 2026, 05:41 PM UTC
Duration
—
Affected: Application
Timeline · 4 updates
  1. investigating Mar 04, 2026, 05:14 PM UTC

    Status: Investigating 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. Affected components Application (Degraded performance)

  2. monitoring Mar 04, 2026, 05:24 PM UTC

    Status: Monitoring Identified the issue and have mitigated the impact. We will continue monitoring and take more follow up actions. Affected components Application (Degraded performance)

  3. monitoring Mar 04, 2026, 05:39 PM UTC

    Status: Monitoring Performance should have returned to normal. We are still monitoring to ensure the experience is restored. Affected components Application (Degraded performance)

  4. resolved Mar 04, 2026, 05:41 PM UTC

    Status: Resolved Issue is resolved. Affected components Application (Operational)

Read the full incident report →

Minor February 26, 2026

[EU] MCP server performance degraded

Detected by Pingoru
Feb 26, 2026, 01:36 PM UTC
Resolved
Feb 26, 2026, 01:36 PM UTC
Duration
—
Affected: MCP server
Timeline · 2 updates
  1. investigating Feb 26, 2026, 01:27 PM UTC

    Status: Investigating 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. Affected components MCP server (Degraded performance)

  2. resolved Feb 26, 2026, 01:36 PM UTC

    Status: Resolved 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. Affected components MCP server (Operational)

Read the full incident report →

Minor February 13, 2026

[AU] Calls to Public API and MCP server are failing

Detected by Pingoru
Feb 13, 2026, 03:45 PM UTC
Resolved
Feb 13, 2026, 03:45 PM UTC
Duration
—
Affected: Application
Timeline · 6 updates
  1. identified Feb 13, 2026, 12:49 PM UTC

    Status: Identified 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. Affected components Application (Degraded performance)

  2. identified Feb 13, 2026, 01:20 PM UTC

    Status: Identified 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. Affected components Application (Degraded performance)

  3. monitoring Feb 13, 2026, 01:31 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  4. monitoring Feb 13, 2026, 01:59 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  5. monitoring Feb 13, 2026, 02:22 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  6. resolved Feb 13, 2026, 03:45 PM UTC

    Status: Resolved 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. Affected components Application (Operational)

Read the full incident report →

Minor February 13, 2026

[EU] Calls to Public API and MCP server are failing

Detected by Pingoru
Feb 13, 2026, 03:45 PM UTC
Resolved
Feb 13, 2026, 03:45 PM UTC
Duration
—
Affected: Application
Timeline · 6 updates
  1. identified Feb 13, 2026, 12:49 PM UTC

    Status: Identified 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. Affected components Application (Degraded performance)

  2. identified Feb 13, 2026, 01:20 PM UTC

    Status: Identified 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. Affected components Application (Degraded performance)

  3. monitoring Feb 13, 2026, 01:31 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  4. monitoring Feb 13, 2026, 01:59 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  5. monitoring Feb 13, 2026, 02:22 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  6. resolved Feb 13, 2026, 03:45 PM UTC

    Status: Resolved 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. Affected components Application (Operational)

Read the full incident report →

Minor February 13, 2026

[US] Calls to Public API and MCP server are failing

Detected by Pingoru
Feb 13, 2026, 03:45 PM UTC
Resolved
Feb 13, 2026, 03:45 PM UTC
Duration
—
Affected: Application
Timeline · 6 updates
  1. identified Feb 13, 2026, 12:49 PM UTC

    Status: Identified 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. Affected components Application (Degraded performance)

  2. identified Feb 13, 2026, 01:20 PM UTC

    Status: Identified 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. Affected components Application (Degraded performance)

  3. monitoring Feb 13, 2026, 01:31 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  4. monitoring Feb 13, 2026, 01:59 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  5. monitoring Feb 13, 2026, 02:22 PM UTC

    Status: Monitoring 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. Affected components Application (Degraded performance)

  6. resolved Feb 13, 2026, 03:45 PM UTC

    Status: Resolved 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. Affected components Application (Operational)

Read the full incident report →

Looking to track Miro downtime and outages?

Pingoru polls Miro's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Miro reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Miro alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Miro for free

5 free monitors · No credit card required