Labrador CMS Outage History

Labrador CMS had 5 outages in the last 2 years totaling 2h 12m of downtime — averaging 0.2 incidents per month.

There were 5 Labrador CMS outages since September 25, 2025 totaling 2h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.labradorcms.com

Critical July 16, 2026

Publishing and updating articles

Detected by Pingoru: Jul 16, 2026, 09:27 AM UTC
Resolved: Jul 16, 2026, 10:59 AM UTC
Duration: 1h 32m

Affected: Labrador Editor

Timeline · 3 updates

monitoring Jul 16, 2026, 09:27 AM UTC

We are currently experiencing issues with publishing and editing articles. The root cause has been identified as an issue with our upstream cloud provider (AWS CloudFront) affecting the delivery of published content. Our team is actively monitoring the situation. We will post updates here as soon as we know more. We apologize for the inconvenience. Issue reported by AWS: https://health.console.aws.amazon.com/health/home#/account/dashboard/open-issues?eventID=arn:aws:health:global::event/CLOUDFRONT/AWS_CLOUDFRONT_OPERATIONAL_ISSUE/AWS_CLOUDFRONT_OPERATIONAL_ISSUE_EDF4C_83808542A4E&eventTab=details
monitoring Jul 16, 2026, 09:29 AM UTC

We are continuing to monitor for any further issues.
resolved Jul 16, 2026, 10:59 AM UTC

We have deployed a fix that restores publishing and editing of articles. The issue was caused by a fault at our cloud provider, and we have rerouted traffic around the affected component. Publishing should now work as normal, though it may be slightly slower than usual while the temporary route is in place. We are continuing to monitor closely and apologize for the disruption.

Read the full incident report →

Critical April 22, 2026

Labrador development environment down

Detected by Pingoru: Apr 22, 2026, 06:52 AM UTC
Resolved: Apr 22, 2026, 07:19 AM UTC
Duration: 27m

Affected: Labdevs Development

Timeline · 3 updates

identified Apr 22, 2026, 06:52 AM UTC

The labrador development environment is currently down due to a full disk. We are in the process of removing data and rebooting the server.
monitoring Apr 22, 2026, 07:06 AM UTC

The dev environment should now be accessible and clusters are slowly coming back up.
resolved Apr 22, 2026, 07:19 AM UTC

The development environment is back up and running with all clusters stable.

Read the full incident report →

Major March 30, 2026

Major outage on infrastructure

Detected by Pingoru: Mar 30, 2026, 07:22 PM UTC
Resolved: Mar 30, 2026, 07:35 PM UTC
Duration: 12m

Affected: Labrador EditorLabrador Frontend

Timeline · 3 updates

monitoring Mar 31, 2026, 09:27 AM UTC

Our infrastructure at OVH experienced issues for some of their Virtual Private Servers instances which affected our connections to the editor/cms for all customers and for some of our customers that are using OVH also for their frontend. We experienced issues from 21.22 CET to 21.35 CET, 30.03.26. For more info, read incident report "[GRA6][Virtual Private Servers] - Some instances incident notification" at OVH "...issue affecting our Virtual Private Servers offer on the specific region GRA6." Incident info: https://bare-metal-servers.status-ovhcloud.com/incidents/s06688dvxskr We are still monitoring the incident
monitoring Mar 31, 2026, 10:42 AM UTC

We are continuing to monitor for any further issues.
resolved Mar 31, 2026, 12:10 PM UTC

No new issues has been reported beyond initial outage

Read the full incident report →

Notice January 21, 2026

Network issues

Detected by Pingoru: Jan 21, 2026, 09:05 AM UTC
Resolved: Jan 20, 2026, 08:30 PM UTC
Duration: —

Timeline · 1 update

resolved Jan 21, 2026, 09:05 AM UTC

From 21:45 - 21:55 CET our infrastructure partner OVH experienced network issues. This led to instability for some of our customers, both on CMS and Front. The issues were solved by OVH and systems were back to normal operation at 21:55 CET.

Read the full incident report →

Major September 25, 2025

Labrador Front service disruptions

Detected by Pingoru: Sep 25, 2025, 11:34 AM UTC
Resolved: Sep 24, 2025, 08:30 PM UTC
Duration: —

Timeline · 1 update

resolved Sep 25, 2025, 11:34 AM UTC

At 24.09.2025 between 22:22-22:49 GMT+2 we experienced service disruptions for Labrador Front, resulting in slower response times and intermittent HTTP errors. The issue was caused by an edge case in our caching layer where, under the right circumstances, the cache would get overwhelmed, causing requests to queue up. We have identified the cause of this issue and have taken immediate action to ensure it will not reoccur.

Read the full incident report →