Last checked: 4 minutes 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: **What happened?** Realtime collaboration failed, resulting in MURAL users not being able to see other logged-in users or their actions in murals. **Summary** At 16:10 UTC on June 10th, we started to receive notifications from MURAL users of an issue with realtime collaboration. MURAL’s task force started investigating at 16:23 UTC. By 16:44 UTC a change had been deployed, restoring realtime collaboration and enabling users to see collaborators in their murals. This change was monitored over the next hour to ensure system stability, after which the incident was considered resolved. The incident lasted for 34 minutes, with an additional 60 minutes of monitoring time to ensure the system remained stable.
Status: Postmortem
Impact: Major | Started At: June 10, 2022, 4:32 p.m.
Description: **What happened?** A small number of customers using BYOK experienced an issue with logging in to the MURAL application. Authentication requests were being redirected from their customer tenants to the main [app.mural.co](http://app.mural.co) tenant, resulting in their users being unable to log in. Initial reports of this were received from MURAL customers on Sunday May 1st. Further reports were received on Monday May 2nd, at which point the issue was classified as a major incident and our task force was engaged. **Summary** MURAL’s task force started investigating at 13:58 UTC on Monday May 2nd. The cause of the issue was identified as being an incorrect configuration in how users on custom tenants were being routed through the login process. Once the issue was identified, a fix was rolled out at 14:07 UTC. This immediately corrected the login flow for clients using BYOK. **What we've done to avoid this happening again** Parts of the login flow for BYOK clients had been hard-coded. We have changed this to be dynamically generated, reducing the risk of code-based errors. We are also researching avenues to improve the automated monitoring of login issues.
Status: Postmortem
Impact: Minor | Started At: May 2, 2022, 1:58 p.m.
Description: 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.
Status: Resolved
Impact: None | Started At: March 23, 2022, 4:30 p.m.
Description: We have implemented a fix for this issue with successful results. We appreciate your patience and apologize for any inconveniences caused during this incident.
Status: Resolved
Impact: Minor | Started At: March 7, 2022, 11 a.m.
Description: **What happened?** On Friday, February 18, 2022, the search engine in MURAL was upgraded from ElasticSearch 6 to ES7. The change proceeded as planned and no immediate issues were detected during our post-release checks. Later that day our engineers detected unexpected behavior with MURAL search results. An immediate decision was taken to roll back to the previous version. The process to roll back the upgrade was unsuccessful. Our team worked through the weekend to restore search functionality within MURAL workspaces. Public API endpoints for searching were however inoperative. Our team continued working through the next week to identify the root of the issue with ElasticSearch. On Friday, February 25, the indexes were fully rebuilt on a new ES6 cluster, tested successfully in beta, and then enabled in production. This restored full functionality using ES6, including the public API endpoints for search. **Summary** This incident resulted in a partial outage for search functionality within MURAL workspaces, lasting 54 hours and 56 minutes. MURAL remained operational throughout this incident and members were able to log in and access their data. **What we've done to avoid this happening again** We are re-evaluating our upgrade process for ES6 to ES7 to ensure this does not happen again during the next upgrade.
Status: Postmortem
Impact: Major | Started At: Feb. 18, 2022, 10:45 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.