Is there an Mural outage?
Mural status: Systems Active
Last checked: a minute ago
Get notified about any outages, downtime or incidents for Mural and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: a minute ago
Get notified about any outages, downtime or incidents for Mural and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Mural.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Learning | Active |
| Website | Active |
| Mural Application | Active |
| Authentication | Active |
| Billing | Active |
| Canvas | Active |
| Exports | Active |
| Integrations | Active |
| Mural Database | Active |
| Notifications | Active |
| Realtime collaboration | Active |
| Search | Active |
View the latest incidents for Mural and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Sept. 16, 2021, 2:24 a.m.
Description: **What happened?** At 06:15 UTC on August 9, 2021, we experienced a spike in CPU usage on our primary database servers. A very large number of simultaneous operations in a single workspace, specifically joining a workspace and moving content between workspaces, generated write conflicts and resulted in the primary database server locking up. Users that were logged in at the time had their sessions terminated and no new login requests could be processed. **Details and corrective actions** We identified the cause of the incident and initiated a fail-over to a new primary database server at 06:44 UTC. This was completed at 07:35 UTC, at which point full service was restored. We immediately started investigating the root cause of the write conflicts and optimizing the workflows for joining workspaces to prevent this from impacting system availability again. **Summary** The outage resulted in 1 hour and 20 minutes of downtime. No data from prior to the outage was lost during this time. **What we’ve done to avoid this happening again** As an immediate action we implemented an optimization to the workflow for joining the impacted workspace. We are working towards applying this update to all workspaces in an upcoming release.
Status: Postmortem
Impact: Critical | Started At: Aug. 9, 2021, 6:35 a.m.
Description: The fix we deployed has successfully resolved the issue with real-time updates in collaboration sessions. If you are continuing to experience difficulties, please refresh your browser window to make sure you're using the latest updates. We are very sorry for the disruption to your collaboration sessions. We will be conducting an in-depth analysis to avoid this happening again.
Status: Resolved
Impact: Major | Started At: July 7, 2021, 7:53 p.m.
Description: The fix we implemented has proven to be successful and MURAL has remained stable. We are closing this incident and starting our analysis into the cause of this issue. We are very sorry for the service interruption and will be taking steps to mitigate this in future.
Status: Resolved
Impact: Critical | Started At: June 9, 2021, 11:47 p.m.
Description: **What happened?** At 17:30 UTC on June 9, 2021, we experienced a spike in CPU usage on our primary database servers. A bulk action in billing groups resulted in the primary database server locking up. Users that were logged in at the time had their sessions terminated and no new login requests could be processed. **Details and corrective actions** At 17:32 UTC we initiated a fail-over to a new primary database server. This was completed at 17:46 UTC, at which time full service was restored with no data loss. **What happened next?** At 23:33 UTC we experienced a similar set of events and the database on the new primary database server became unresponsive. **Details and corrective actions** At 23:42 UTC we initiated a fail-over to another new primary database server. This was completed at 23:56 UTC, at which time full service was restored with no data loss. **Summary** The first outage resulted in 16 minutes of downtime, with another 23 minutes of downtime for the second outage. **What we’ve done to avoid this happening again** Following the outage on May 19, we performed a series of maintenance operations over the weekend of May 22-23 to significantly improve our database performance. This reduced the likelihood of a similar outage in future, whilst not entirely eliminating it. As an immediate remedial action, we have temporarily disabled the bulk change functionality in billing groups \(an Enterprise Network feature\). This functionality is being refactored and will be re-released as soon as possible. We are also conducting a comprehensive review of bulk operations within the MURAL platform to ensure this cannot happen again.
Status: Postmortem
Impact: Critical | Started At: June 9, 2021, 5:35 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
