Intuto incident
Microsoft Azure Outage Impacting Intuto Sites
Intuto experienced a critical incident on October 29, 2025 affecting Networking and Hosting Infrastructure, lasting 1d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 29, 2025, 05:54 PM UTC
The previous issue has recurred. Contact with our infrastructure providers confirms the root cause is an upstream DNS service error within the Azure platform. We are currently monitoring the Azure status for updates regarding resolution.
- monitoring Oct 29, 2025, 07:07 PM UTC
Microsoft has reported that they are rolling out updates to resolve this outage. "We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery." We will continue to monitor the platform and will share further updates here. https://azure.status.microsoft/en-gb/status
- monitoring Oct 29, 2025, 09:33 PM UTC
Microsoft has reported that the deployment of the 'last known good' configuration has successfully completed. They are now actively recovering nodes and re-routing traffic through healthy infrastructure to restore full operational scale. Recovery is a gradual process, and while signs of improvement are present, intermittent failures may persist. Full recovery is currently expected by 23:30 UTC on 29 October 2025. We will continue to monitor the platform and will share further updates here.
- monitoring Oct 29, 2025, 11:24 PM UTC
Microsoft are continuing to monitor the resolution. We can confirm that some of our core infrastructure is hosted on services listed in the scope of affected Azure components. We continue to monitor the platform and will share further updates here.
- investigating Oct 30, 2025, 03:17 AM UTC
Microsoft has resolved its incident, and we have seen a reduction in errors across the site. However, we still see this error occurring. We are investigating to determine if the issue is in fact resolved and this is just a lingering effect, or if a separate, unrelated issue is at play. We will continue to monitor the platform and will share further updates here.
- investigating Oct 30, 2025, 05:57 AM UTC
We can see a reduced number of requests still receiving this error. Platform monitoring will continue overnight, while we further our investigations with our partners. Our next update to this status will be provided by 9:00 AM 31st October NZT, unless circumstances necessitate an earlier update.
- identified Oct 30, 2025, 06:15 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 30, 2025, 07:03 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 30, 2025, 08:03 PM UTC
This incident has now been resolved. A post incident report will be provided within 5 business days. Thanks for your patience while we resolved this issue.
- postmortem Nov 02, 2025, 08:18 PM UTC
## 🚨 Post Incident Report \(PIR\) - Intuto Service Disruption \(Oct 29 - Oct 31\) This report provides analysis of the intermittent service disruption that affected the Intuto platform from October 29th to October 31st. ### **Incident Summary** A platform update on the 28th October, introduced a logic error in the application's configuration handling. This logic issue incorrectly updated a global setting with a tenant-specific Content Security Policy \(CSP\) domain. As concurrent multi-tenant usage increased, the domains listed in the global CSP setting continuously grew in size, causing intermittent service failures characterised by `HTTP 520` and `HTTP 503` errors. The complexity and duration of the resolution were significantly compounded by a concurrent, global Microsoft Azure App Services outage. The external outage began during the initial internal investigation, introducing its own set of confusing errors and temporarily diverting diagnostic efforts, which ultimately delayed the identification and correction of the internal application root cause. ### **Immediate Action Items** **✅ Engineering:** Review all affected global application settings that are dynamically modified at runtime to ensure correct isolation and scoping. **✅ QA/Testing:** Evaluate current QA procedures for features involving dynamic tenant-scoped application configurations.