- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Mural. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2022-03-23 17:38 UTC and 2022-03-23 16:30 UTC may need a replay.Subscribe to Mural's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=mural works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Mural 1
- resolved
What happened? At 16:13 UTC on Wednesday 23rd March we detected a latency increase in the MURAL application. This resulted in collaboration sessions being terminated and users being unable to log back in to MURAL. MURAL's engineers quickly identified the cause of the increased latency and deployed a fix. Latency returned to normal levels and full service was resumed at 16:30 UTC. MURAL will be conducting an in-depth root cause analysis to determine how to prevent this issue from occurring again.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d9aa9e4219
Is Mural still down?
No, this incident was resolved 2022-03-23 16:30 UTC. For Mural's live state, see https://down.guide/providers/mural.
How long did it last?
0m, from 2022-03-23 17:38 UTC to 2022-03-23 16:30 UTC, by the times Mural posted.
What caused it?
Mural hasn't published a root cause. If it does, it shows here.
Where does this come from?
Mural's official status page, https://status.mural.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.