Labrador CMS Outage History

Labrador CMS is up right now

Labrador CMS had 10 outages in the last 2 years totaling 3h 53m of downtime — averaging 0.4 incidents per month.

There were 10 Labrador CMS outages since August 20, 2024 totaling 3h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.labradorcms.com

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
  1. 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.

  2. monitoring Apr 22, 2026, 07:06 AM UTC

    The dev environment should now be accessible and clusters are slowly coming back up.

  3. 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
  1. 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

  2. monitoring Mar 31, 2026, 10:42 AM UTC

    We are continuing to monitor for any further issues.

  3. 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
  1. 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
  1. 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 →

Major April 28, 2025

Service disruptions

Detected by Pingoru
Apr 28, 2025, 11:49 AM UTC
Resolved
Apr 28, 2025, 12:19 PM UTC
Duration
30m
Affected: Labrador EditorLabrador Frontend
Timeline · 3 updates
  1. investigating Apr 28, 2025, 11:49 AM UTC

    Labrador CMS is currently experiencing partial service disruptions. We are looking into this issue and will update you as soon as we know more.

  2. monitoring Apr 28, 2025, 12:14 PM UTC

    The problem has been identified. Too aggressive use of our import APIs resulted in a subset of customers to experience problems with database connections. The API-usage has been dialed down and operations should shortly return to normal. We will continue to monitor performance.

  3. resolved Apr 28, 2025, 12:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 13, 2025

Network incident AWS Stockholm

Detected by Pingoru
Feb 13, 2025, 11:10 PM UTC
Resolved
Feb 14, 2025, 12:25 AM UTC
Duration
1h 15m
Affected: Labrador Frontend
Timeline · 2 updates
  1. monitoring Feb 14, 2025, 01:26 AM UTC

    Customers hosted within our AWS Stockholm region experienced service disruptions this night between 00:10-01:25 CET caused by a networking incident at AWS. A fix has been implemented, all services are operational again and we are monitoring the situation. More details: https://health.aws.amazon.com/health/status?eventID=arn:aws:health:eu-north-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_6337A_0CF62E5431F

  2. resolved Feb 14, 2025, 07:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 19, 2025

Apex redirect issues

Detected by Pingoru
Jan 19, 2025, 10:14 PM UTC
Resolved
Jan 19, 2025, 10:14 PM UTC
Duration
—
Affected: Labrador Frontend
Timeline · 1 update
  1. resolved Jan 19, 2025, 10:14 PM UTC

    Some customers experienced an issue where readers would not be redirected to www.domainname.tld when trying to access domainname.tld. The error has been identified and systems are back to normal operation again.

Read the full incident report →

Major August 20, 2024

Editor disruptions

Detected by Pingoru
Aug 20, 2024, 10:17 AM UTC
Resolved
Aug 19, 2024, 03:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 20, 2024, 10:17 AM UTC

    As one of our physical servers experienced hardware problem and was taken offline, the automatic failover functionality was caught in a bad state and needed to be restarted manually. This led to some of our customers experiencing intermittent failures in the CMS and being unable to log in and publish articles. The affected physical server has now been repaired and the failover component is being further improved to prevent a similar incident in the future.

Read the full incident report →