{
"vendor": "Mural",
"slug": "mural",
"platform": "statuspage",
"status_url": "https://status.mural.co",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "ok",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "Update 2 - The fix to the SSO SAML login issue that caused an Authentication Error has been implemented. We now believe the issue is resolved but will continue to monitor throughout the day.\n\nPlease check our status page for the most up-to-date info: status.mural.co",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-04T18:37:35.337-03:00",
"resolved_inferred": false,
"started_at": "2026-08-04T18:01:33.000-03:00",
"state": "resolved",
"title": "Authentication Error for some SAML SSO users",
"updated_at": "2026-08-04T18:37:35.354-03:00",
"url": "https://stspg.io/p02p0fbkb4k3"
},
{
"body": "The fix our 3rd party provider implemented earlier has been successful in resolving the issue and full service has been resolved.\n\nWe apologize for the inconvenience this interruption caused.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-17T16:16:13.125-03:00",
"resolved_inferred": false,
"started_at": "2026-04-17T13:13:58.599-03:00",
"state": "resolved",
"title": "Some users are unable to sign in to Mural",
"updated_at": "2026-04-17T16:16:13.139-03:00",
"url": "https://stspg.io/t4rbxcsykm35"
},
{
"body": "The fix we implemented earlier has been successful in resolving the issue and full service has been resolved.\n\nWe apologize for the inconvenience this interruption caused, and will be conducting a full review to avoid a repeat in the future.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-26T11:24:53.227-03:00",
"resolved_inferred": false,
"started_at": "2026-03-26T10:24:30.481-03:00",
"state": "resolved",
"title": "Mural Collaboration Issue - murals not loading",
"updated_at": "2026-03-26T11:24:53.243-03:00",
"url": "https://stspg.io/zv0fmg0n1g22"
},
{
"body": "Users receiving the \"Offline\" message are now able to access content and create new murals, and no new examples of this issue are reported. This issue is now considered fully resolved.\n\nWe apologize for the inconvenience this interruption caused and will be conducting a full review to identify potential improvements for incidents of this nature.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-25T09:05:21.376-03:00",
"resolved_inferred": false,
"started_at": "2025-11-25T07:04:21.041-03:00",
"state": "resolved",
"title": "Some users are receiving an \"Offline\" message when working in Mural",
"updated_at": "2025-11-25T09:05:21.393-03:00",
"url": "https://stspg.io/sl1yzxt8f3gx"
},
{
"body": "**Date:** October 29, 2025  \n**Impact Duration:** 15:55 \u2013 21:20 UTC  \n**Status:** Resolved  \n**Root Cause:** Outage with our cloud hosting provider\n\n### **Overview**\n\nOn **October 29, 2025**, Mural experienced a major service disruption that prevented users from signing in or accessing their murals. The issue was caused by a widespread outage with our primary cloud hosting provider.\n\nWhile the outage was external to Mural, it significantly impacted our ability to serve requests and maintain normal operations for several hours.\n\n### **Timeline of Events \\(UTC\\)**\n\n* **15:55** \u2014 We detected that some users were unable to sign in to Mural. Mural\u2019s incident response team began investigating immediately\n* **16:13** \u2014 The incident notification was posted to Mural\u2019s status page at [status.mural.co](http://status.mural.co)\u00a0\n* **16:17** \u2014 We identified the root cause as an outage in Microsoft Azure\u2019s infrastructure affecting application access\n* **16:32 \u2013 20:46** \u2014 We continued working with Microsoft Azure and monitored for recovery while keeping users informed via our status page\n* **20:46** \u2014 Partial recovery began; some regions regained access\n* **21:19** \u2014 Full service restoration confirmed\n* **23:20** \u2014 Incident marked as **resolved** after stable monitoring and confirmation from our upstream provider\n\n### **Root Cause**\n\nThe outage originated from an **Azure Front Door incident** that disrupted network resources across several regions. This affected authentication and access for users attempting to sign in to Mural. Our systems rely on Azure for critical infrastructure, meaning our service availability was directly impacted by the Azure outage.\n\n### **Resolution**\n\nWe attempted several workarounds during the Azure outage, however these proved unsuccessful as the core issue required Azure Front Door accessibility. As Azure recovered, we were able to reconfigure our systems to bring Mural services back online. We closely monitored all internal systems and user traffic to ensure full stability before marking the incident as \u2018in monitoring\u2019. Once normal operation was confirmed across all regions for a period of 2 hours, we closed the incident.\n\n### **What We\u2019re Doing Next**\n\nAlthough this incident was triggered by an external provider, we are taking several steps to reduce the impact of similar events in the future:\n\n1. **CDN Improvements** \u2014 We are researching improvements to our content delivery network \\(CDN\\) setup to enhance resilience\n2. **Enhanced Monitoring** \u2014 We are expanding our monitoring systems to detect upstream provider issues faster and more precisely\n3. **Communication Consistency** \u2014 We are working on improving how we communicate during incidents across all channels, including our status page, marketing site, and in-app messages, to ensure consistent and timely updates\n4. **Cloud Infrastructure** \u2014 We continue to assess our infrastructure to mitigate any potential impact from potential future impacts to our cloud hosting provider\n\n### **Closing Thoughts**\n\nWe know how important Mural is for your daily collaboration and creative work. Any downtime disrupts your teams, and we take that responsibility seriously. We sincerely apologize for the inconvenience this incident caused and appreciate your patience as we worked to resolve it.\n\nWe\u2019re committed to learning from this event and strengthening Mural\u2019s resilience against external dependencies.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-29T20:28:53.452-03:00",
"resolved_inferred": false,
"started_at": "2025-10-29T13:13:19.051-03:00",
"state": "postmortem",
"title": "Users are unable to sign in to Mural",
"updated_at": "2025-11-04T10:22:56.832-03:00",
"url": "https://stspg.io/j2dq4dwt03kw"
},
{
"body": "Full service to our www.mural.co website has been restored. We'll continue to monitor the situation throughout the day in case any further remedial actions are needed.\n\nWe apologize for any inconvenience this may have caused and thank you for your patience whilst we're worked to resolve the issue.\n\nWe're pleased to note that our Mural app under app.mural.co was not affected by this incident and users were able to log in throughout this period.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-20T15:30:34.956-03:00",
"resolved_inferred": false,
"started_at": "2025-10-20T12:45:09.146-03:00",
"state": "resolved",
"title": "Mural website service interruption - login still available under app.mural.co",
"updated_at": "2025-10-20T15:30:34.972-03:00",
"url": "https://stspg.io/sg1ffx9284tc"
}
]
}