Is Mural Down?
- Mural's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 526 ms
Right now
The verdict is the worse of these two. How we decide
Mural's status page
status.mural.co · read · checked every 3 minutes
| Component | Status |
|---|---|
| Authentication | Operational |
| Billing | Operational |
| Canvas | Operational |
| Dashboard | Operational |
| Exports | Operational |
| Integrations | Operational |
| Mural Database | Operational |
| Notifications | Operational |
| Realtime collaboration | Operational |
| Search | Operational |
| Learning | Operational |
| Website | Operational |
FlareWarden checks
app.mural.co from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 526 ms
- Checked
By region
- Ashburn reachable, 133 ms
- Chicago reachable, 174 ms
- Frankfurt reachable, 432 ms
- Johannesburg reachable, 1015 ms
- London reachable, 357 ms
- Los Angeles reachable, 342 ms
- São Paulo reachable, 786 ms
- Tokyo reachable, 973 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 32 ms | 3 ms | 8 ms | 132 ms |
| Chicago | 61 ms | 18 ms | 21 ms | 156 ms |
| Frankfurt | 48 ms | 92 ms | 94 ms | 417 ms |
| Johannesburg | 46 ms | 241 ms | 241 ms | 1002 ms |
| London | 34 ms | 77 ms | 80 ms | 344 ms |
| Los Angeles | 68 ms | 63 ms | 66 ms | 325 ms |
| São Paulo | 287 ms | 118 ms | 124 ms | 766 ms |
| Tokyo | 293 ms | 166 ms | 169 ms | 960 ms |
History
Incidents Mural reported
Since Oct 22, 2 days · from status.mural.co
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Mural website availability
Measured by FlareWarden · app.mural.co
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 549ms
Last 30 days
72-day clean streakMeasured by FlareWarden's own checks of app.mural.co from multiple regions every 6 hours. Mural's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 72 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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 up to 17 cities across three regions to find out where it breaks.
Related services
Mural outage FAQ
Is Mural down or is my board just not syncing?
Will work done during a sync outage be saved?
Why did SAML single sign-on fail when the app is up?
Does an outage affect exports and integrations?
How we measure this
- We request Mural's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Mural itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Mural goes down
We check Mural every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring