Performance degraded & Syst...

Update timeline

1. investigating Mar 30, 2026, 06:00 AM UTC

   Performance of the platform is currently degraded.

2. resolved Mar 30, 2026, 04:45 PM UTC

   Post-Mortem: Service Disruption – March 30, 2026 Duration: 8:00 AM – 4:36 PM CEST Severity: Major Affected: app.langdock.com Status: Resolved What Happened On March 30, 2026, Langdock experienced a major service disruption caused by a platform-level degradation on Azure Container Apps (ACA). Containers that normally start in under 2 minutes took over 15 minutes during the incident, preventing our autoscaler from bringing new capacity online and leading to a full platform outage from approximately 11:30 AM CEST. Timeline (CEST) 8:00 AM — Performance degradation detected 9:15 AM — Issue identified; hotfix deployed 9:43 AM — Performance stabilised, partial recovery 9:55 AM — Downstream issues discovered; investigation continues 10:45 AM — Core platform restored; workflows & file uploads still affected 11:30 AM — Full platform outage begins due to cascading downstream effects from increased startup time of ACA. 12:11 PM — Platform taken fully offline for controlled reboot 3:34 PM — Platform restored and accepting traffic 4:36 PM — Workflows and file uploads fully restored 4:37 PM — Incident fully resolved Root Cause Azure Container Apps experienced a platform-level degradation affecting container startup times. The same container image started in under 30 seconds on AKS, confirming the issue was with ACA and not our application. Resolution & Next Steps We relaxed startup probes, raised the minimum container count, and temporarily disabled readiness/liveness probes to restore service. We are now implementing improved failover paths, improved startup monitoring, and better baseline capacity provisioning to prevent a recurrence. We sincerely apologize for the disruption. Please reach out to [email protected] with any questions.