Skip to main content
Miro logo

Is Miro Down?

No — Miro is up

Reachable from all 7 checked regions

Average response time: 973ms

Last checked · checks run every 6 hours

Official status page: https://status.miro.com

Miro uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1148ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 20 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

dfw
1170ms
DNS 9ms TCP 6ms TLS 8ms TTFB 687ms
ewr
421ms
DNS 89ms TCP 1ms TLS 3ms TTFB 374ms
fra
838ms
DNS 20ms TCP 0ms TLS 3ms TTFB 776ms
gru
2135ms
DNS 336ms TCP 9ms TLS 11ms TTFB 1217ms
iad
445ms
DNS 46ms TCP 1ms TLS 4ms TTFB 363ms
jnb
1966ms
DNS 81ms TCP 0ms TLS 2ms TTFB 496ms
lax
670ms
DNS 151ms TCP 1ms TLS 3ms TTFB 535ms
lhr
468ms
DNS 38ms TCP 6ms TLS 8ms TTFB 398ms
nrt
1838ms
DNS 152ms TCP 2ms TLS 4ms TTFB 628ms

What Miro does

Miro is an online whiteboard where distributed teams run workshops, retrospectives and design sessions on an infinite canvas edited by many people at once. Its value is concentrated in live sessions, so an outage does not merely postpone work: it ends a meeting that a dozen people had already joined.

What an outage looks like

Boards fail to open, or open blank while the toolbar renders. Other people's cursors freeze and their changes stop arriving, so a board looks abandoned rather than broken. Sticky notes added locally vanish on reconnect. Exports and embeds fail, and the mobile and desktop apps report connection errors while a stale board stays on screen.

What to do about it

Check status.miro.com and select your data residency region, since Miro reports separately for the EU, US and AU and your account is tied to one. If a workshop is mid-flight, switch to another surface rather than waiting, and photograph or export the board only once the service returns. Avoid rebuilding content on a second board that will then need merging.

Is it down for everyone, or just you?

If this page says Miro is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Figma
Figma
Notion
Notion
Zoom
Zoom
Slack
Slack

Miro outage FAQ

Is Miro down or has my board stopped syncing?
A board that renders but shows no one else's cursor is usually a sync failure rather than a fully unavailable service, and it looks alarmingly like an empty room. Check status.miro.com for your data residency region. Reloading the tab is worth trying once, but repeated reloads risk discarding local changes that had not yet been delivered.
Which region do I check on Miro's status page?
Miro reports by data residency region, offering EU, US and AU, and your organisation was assigned one when the account was created. An incident in a region you do not use will not affect you. Reading the wrong region is the quickest way to conclude Miro is healthy while your own team cannot open a board.
Will I lose the sticky notes added during an outage?
Changes the client accepted but could not send may sync when the connection returns, or may be discarded if you refresh first. Keep the tab open rather than reloading it. For a workshop where the content matters, taking a screenshot before touching anything preserves the thinking even if the board itself rolls back.
What should we do if Miro fails mid-workshop?
Move the conversation rather than the tooling. A shared document, a call with screen sharing, or even a photographed physical wall keeps the session going, and the output can be transferred afterwards. Rebuilding the board live on a second Miro board tends to create two partial boards that someone has to merge later.
Do Miro embeds on other sites break during an outage?
Yes. An embedded board is loaded from Miro, so a page containing one shows a failed frame while the rest of the page renders normally. This is a common way people discover a Miro incident without using Miro. Nothing on the host page needs changing; the embed recovers on its own when the service does.

How we measure this

  • We request Miro's public endpoint every 6 hours from Fly.io regions across six continents — 7 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Miro publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Miro goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required