Langdock Outage History

Langdock is up right now

There were 9 Langdock outages since February 15, 2026 totaling 37h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.langdock.com

Major April 27, 2026

Langdock is unavailable

Detected by Pingoru
Apr 27, 2026, 06:30 PM UTC
Resolved
Apr 27, 2026, 06:51 PM UTC
Duration
21m
Affected: Current status by service (app.langdock.com)Current status by service (api.langdock.com)Current status by service (Workflows Runtime)
Timeline · 2 updates
  1. investigating Apr 27, 2026, 06:30 PM UTC

    We're currently experiencing issues and Langdock is unavailable for all users. We're investigating and will keep you updated.

  2. resolved Apr 27, 2026, 06:51 PM UTC

    We have identified the root cause and fixed the issue. We experienced a failed database migration which caused some services not to start correctly. Langdock is available again for all users. We will continue to monitor the situation.

Read the full incident report →

Minor April 13, 2026

Workflow runs high error rate

Detected by Pingoru
Apr 13, 2026, 06:15 PM UTC
Resolved
Apr 14, 2026, 06:26 AM UTC
Duration
12h 11m
Affected: Current status by service (Workflows Runtime)
Timeline · 2 updates
  1. investigating Apr 13, 2026, 06:15 PM UTC

    We are investigating a high error rate across Workflow runs.

  2. resolved Apr 14, 2026, 06:26 AM UTC

    We have identified the issue and released a fix. This issue is resolved.

Read the full incident report →

Minor March 30, 2026

Workflow execution and file...

Detected by Pingoru
Mar 30, 2026, 01:51 PM UTC
Resolved
Mar 30, 2026, 02:36 PM UTC
Duration
45m
Affected: Current status by service (app.langdock.com)
Timeline · 2 updates
  1. investigating Mar 30, 2026, 01:51 PM UTC

    Our workflow execution and file processing services are currently under a lot of load due to the incident earlier in the day. We expect the execution backlog to clear over the next hours.

  2. resolved Mar 30, 2026, 02:36 PM UTC

    The backlog has been processed. File uploads and workflows are running normally again.

Read the full incident report →

Major March 30, 2026

Performance degraded & Syst...

Detected by Pingoru
Mar 30, 2026, 06:00 AM UTC
Resolved
Mar 30, 2026, 04:45 PM UTC
Duration
10h 45m
Affected: Current status by service (app.langdock.com)
Timeline · 2 updates
  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.

Read the full incident report →

Minor March 18, 2026

Web search not working

Detected by Pingoru
Mar 18, 2026, 05:58 PM UTC
Resolved
Mar 18, 2026, 07:16 PM UTC
Duration
1h 18m
Affected: Current status by service (app.langdock.com)
Timeline · 2 updates
  1. investigating Mar 18, 2026, 05:58 PM UTC

    We are aware of an issue where the web search in chat and workflows is not producing results. We are currently working on a fix for this issue.

  2. resolved Mar 18, 2026, 07:16 PM UTC

    We have identified the root cause of the issue and released a fix.

Read the full incident report →

Major February 15, 2026

Login partly unavailable

Detected by Pingoru
Feb 15, 2026, 07:15 PM UTC
Resolved
Feb 16, 2026, 07:51 AM UTC
Duration
12h 36m
Affected: Current status by service (app.langdock.com)
Timeline · 2 updates
  1. investigating Feb 15, 2026, 07:15 PM UTC

    At the moment login is only possible via Microsoft. We are working on restoring the usual login and will update as we have more information.

  2. resolved Feb 16, 2026, 07:51 AM UTC

    We have identified the root cause and restored the normal login flow.

Read the full incident report →

Looking to track Langdock downtime and outages?

Pingoru polls Langdock's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Langdock reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Langdock alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Langdock for free

5 free monitors · No credit card required