Outage in Labrador CMS
Editor disruptions
Resolved MajorIncident Report
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.
Need to monitor Labrador CMS outages?
- Monitor all your external dependencies in one place
- Get instant alerts when outages are detected
- Be the first to know if service is down
- Show real-time status on private or public status page
- Keep your team informed
Latest Updates ( sorted recent to last )
RESOLVED
over 1 year ago - at 08/20/2024 10:17AM
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.
Latest Labrador CMS outages
Network issues - about 1 month ago
Labrador Front service disruptions - 5 months ago
Service disruptions - 10 months ago
Network incident AWS Stockholm - about 1 year ago
Network issues - about 1 year ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with
