Mural status history
Current state: operational — “All Systems Operational” per https://status.mural.co (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Mural incidents last?
From 6 incidents with a vendor-posted start and resolve time. Longest on record: Users are unable to sign in to Mural — 7.2 h (2025-10-29 16:13 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (6)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-04 21:01 UTC | Authentication Error for some SAML SSO users | resolved | major | 36 min |
| 2026-04-17 16:13 UTC | Some users are unable to sign in to Mural | resolved | minor | 3 h 02 min |
| 2026-03-26 13:24 UTC | Mural Collaboration Issue - murals not loading | resolved | major | 1 h 00 min |
| 2025-11-25 10:04 UTC | Some users are receiving an "Offline" message when working in Mural | resolved | major | 2 h 01 min |
| 2025-10-29 16:13 UTC | Users are unable to sign in to Mural | postmortem | critical | 7 h 15 min |
| 2025-10-20 15:45 UTC | Mural website service interruption - login still available under app.mural.co | resolved | major | 2 h 45 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Mural with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"mural"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
