We started checking Miro on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Miro reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Miro's own status page declared. Below it, any public chatter we saw about Miro and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Miro's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Miro in the last 24 hours, which is not evidence that nothing is wrong.
Miro's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Miro's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Miro next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
731
US-West
100.00%
579
Europe
100.00%
530
Asia-Pacific
100.00%
320
Their declared record
Miro's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Sign-in with username and password is unavailablePartial outage
Sep 8, 2026, 7:21 PM UTC to Sep 9, 2026, 2:24 PM UTC (19h 3m)resolved
their latest update (Sep 9, 2026, 2:24 PM 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
Intermittent Issues with User Registration and LoginPartial outage
Aug 31, 2026, 2:31 PM UTC to Aug 31, 2026, 3:57 PM UTC (1h 26m)resolved
their latest update (Aug 31, 2026, 3:57 PM UTC): The issue affecting user registrations and logins has been resolved. Normal system operations have resumed.
Functionality degradation in Miro AIMinor incident
May 21, 2026, 3:14 PM UTC to May 21, 2026, 6:56 PM UTC (3h 42m)resolved
their latest update (May 21, 2026, 6:56 PM 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.
Miro is partially downPartial outage
May 4, 2026, 4:23 PM UTC to May 4, 2026, 7:01 PM UTC (2h 37m)resolved
their latest update (May 4, 2026, 7:01 PM 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.
Some users experienced issues with AI featuresPartial outage
Apr 28, 2026, 3:14 PM UTC to Apr 28, 2026, 3:38 PM UTC (24 min)resolved
their latest update (Apr 28, 2026, 3:38 PM 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.
Board access issueMinor incident
Mar 12, 2026, 4:40 PM UTC to Mar 12, 2026, 7:49 PM UTC (3h 9m)resolved
their latest update (Mar 12, 2026, 7:49 PM UTC): Incident was resolved. Thank you for your patience. Board functionality is back to normal.
Issue affecting our service performanceMinor incident
Mar 4, 2026, 5:14 PM UTC to Mar 4, 2026, 5:41 PM UTC (27 min)resolved
their latest update (Mar 4, 2026, 5:41 PM UTC): Issue is resolved.
MCP server performance degradedMinor incident
Feb 26, 2026, 1:27 PM UTC to Feb 26, 2026, 1:36 PM UTC (9 min)resolved
their latest update (Feb 26, 2026, 1:36 PM 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.
Calls to Public API and MCP server are failingMinor incident
Feb 13, 2026, 12:49 PM UTC to Feb 13, 2026, 3:45 PM UTC (2h 55m)resolved
their latest update (Feb 13, 2026, 3:45 PM 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.
Jan 22, 2026, 5:31 PM UTC to Jan 22, 2026, 10:13 PM UTC (4h 43m)resolved
their latest update (Jan 22, 2026, 10:13 PM 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.
Showing the 10 most recent of 25 incidents Miro has declared in the history we hold.
These entries are Miro's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Miro's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.