Publishing and updating articles
Affected: Labrador Editor
Labrador CMS Outage History
Labrador CMS is up right nowLabrador CMS had 11 outages in the last 2 years totaling 5h 25m of downtime — averaging 0.5 incidents per month.
There were 11 Labrador CMS outages since August 20, 2024 totaling 5h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.
Labrador development environment down
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.
Major outage on infrastructure
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
Network issues
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.
Labrador Front service disruptions
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.
Degraded front performance
Affected: Labrador EditorLabrador Frontend
Timeline · 5 updates
Service disruptions
Affected: Labrador EditorLabrador Frontend
Timeline · 3 updates
- 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.
- 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.
- resolved Apr 28, 2025, 12:19 PM UTC
This incident has been resolved.
Network incident AWS Stockholm
Affected: Labrador Frontend
Timeline · 2 updates
- 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
- resolved Feb 14, 2025, 07:53 AM UTC
This incident has been resolved.
Apex redirect issues
Affected: Labrador Frontend
Timeline · 1 update
- 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.
Service outage due to network issues
Affected: Labrador EditorLabdevs DevelopmentLabrador Frontend
Timeline · 4 updates
Editor disruptions
Timeline · 1 update
- 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.