Skip to main content

Is Mural Down?

No — Mural is up

Reachable from all 8 checked regions

Average response time: 515ms

Last checked · checks run every 6 hours

Official status page: https://status.mural.co

Mural uptime

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

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 12 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

12-day clean streak
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: 100.00% uptime, 16 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 40 checks
Aug 15: 100.00% uptime, 24 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 28 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 24 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Aug 24: no data
Jul 26 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
302ms
DNS 122ms TCP 40ms TLS 46ms TTFB 288ms
ewr
316ms
DNS 148ms TCP 37ms TLS 42ms TTFB 303ms
fra
440ms
DNS 50ms TCP 96ms TLS 95ms TTFB 425ms
gru
499ms
DNS 10ms TCP 119ms TLS 126ms TTFB 486ms
iad
146ms
DNS 115ms TCP 7ms TLS 6ms TTFB 143ms
jnb
1351ms
DNS 178ms TCP 244ms TLS 248ms TTFB 1157ms
lax
264ms
DNS 16ms TCP 57ms TLS 62ms TTFB 250ms
lhr
404ms
DNS 58ms TCP 82ms TLS 87ms TTFB 391ms
nrt
703ms
DNS 9ms TCP 172ms TLS 173ms TTFB 689ms

What Mural does

Mural is an online whiteboard for workshops, retrospectives and design sessions, where several people edit the same canvas at once. Its status page separates Realtime collaboration from the Canvas and the Mural Application, which reflects how outages are actually experienced: the board can open and render while other people's changes stop appearing.

What an outage looks like

Sticky notes and edits from other participants stop appearing while your own still move, which is the signature of a realtime collaboration fault rather than a full outage. Boards fail to open from the dashboard, or open empty. SAML single sign-on rejects logins while direct accounts work. Exports to PDF or image queue without completing.

What to do about it

Check status.mural.co and match the component: Realtime collaboration for changes not syncing, Canvas for boards that will not render, Authentication for login failures. If a workshop is in progress and realtime is degraded, stop editing rather than working around it, because concurrent edits made during a sync fault are the ones most likely to conflict. Exports is a separate line.

Is it down for everyone, or just you?

If this page says Mural 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

Mural outage FAQ

Is Mural down or is my board just not syncing?
Mural reports Realtime collaboration separately from the Mural Application and Canvas, and a sync fault is the more common failure. If the board opens and you can move your own stickies but nobody else's changes appear, that is realtime rather than a full outage. Check that line on status.mural.co before restarting the session.
Will work done during a sync outage be saved?
Edits that never reached the server are not saved, and they are hardest to spot during a realtime fault because your own view looks correct. If the Realtime collaboration line is red, treat anything added since as unconfirmed. Once the component recovers, reload the board and compare it against what you remember adding before continuing.
Why did SAML single sign-on fail when the app is up?
Authentication is its own component, separate from the Mural Application, and Mural has reported an authentication error affecting SAML SSO users while the rest of the platform stayed operational. If your organisation signs in through an identity provider and login fails, check the Authentication line before raising it with your own IT team.
Does an outage affect exports and integrations?
Exports and Integrations are listed as separate components, so a PDF or image export can queue indefinitely while boards work normally, and integrations can break on their own. If an export has not arrived, check the Exports line rather than repeating the request, since a queued export may complete once the component recovers.

How we measure this

  • We request Mural's public endpoint every 6 hours from Fly.io regions across six continents — 8 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 Mural publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Mural 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