Is Labrador CMS down?
Last checked 1m agoNo incidents right now.
Labrador CMS is operational right now. Last checked 1m ago; the most recent incident resolved 10d ago.
Real-time Labrador CMS status, recent outages, and incident history: pulled directly from Labrador CMS's official status page at status.labradorcms.com every 5 minutes. Pingoru tracks 3 Labrador CMS services and has captured 2 incidents in the last 90 days (98.89% uptime). Get email, Slack, Discord, or webhook alerts the moment Labrador CMS reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Labrador Editor
Timeline · 5 updates
- investigating · Oct 21, 2026, 01:50 PM UTC
Due to a worldwide active exploit in part of the software we use in our infrastructure we have turned on an extra level of security on all CMS instances. This will require an extra user/password for all users of Labrador. This will not affect readers or external services using our front APIs, but it WILL be needed for all requests to your CMS, including CMS-APIs. We will share the required credentials to all customers, but if you have not received it yet, send an email to [email protected]
- investigating · Oct 21, 2026, 01:51 PM UTC
We are continuing to investigate this issue.
- identified · Oct 21, 2026, 04:07 PM UTC
We have implemented the patch and will roll it out to all customers now. When all customers have received the patch we will remove the extra layer of security.
- monitoring · Oct 21, 2026, 07:21 PM UTC
All customers have been upgraded, we are rolling out removal of the extra security layer now.
- resolved · Oct 21, 2026, 08:17 PM UTC
All affected services have now been patched and the extra security layer has been removed.
Latest: All affected services have now been patched and the extra security layer has been removed.
-
- Labrador Frontend
Timeline · 4 updates
- investigating · Oct 20, 2026, 11:51 AM UTC
We are experiencing an increased level of 503s on our APIs and are currently investigating. This may affect internal API-requests for automatic fronts and similar.
- identified · Oct 20, 2026, 12:32 PM UTC
We have identified the issue and are currently working on a fix.
- monitoring · Oct 20, 2026, 01:06 PM UTC
The fix has been deployed and we are monitoring the situation. Services should be going back to normal again.
- resolved · Oct 20, 2026, 01:13 PM UTC
The incident has been resolved. "Most read"-lists may take some time to come back due to cache, but everything will be back to normal shortly.
Latest: The incident has been resolved. "Most read"-lists may take some time to come back due to cache, but everything will be back to normal shortly.
-
Incident record
Since April 2026 · Statuspage by Atlassian · 3 components checked every 5 minutesThe longest incident in the last year, Security upgrade on October 21, 2026, ran for 6 hours.
Most affected components, last 12 months
- Labrador Editor3
- Labrador Frontend2
- Labdevs Development1
Latest incidents
- Security upgrade
Due to a worldwide active exploit in part of the software we use in our infrastructure we have turned on an extra level of security on all CMS instances. This…
- Degraded API performance
We are experiencing an increased level of 503s on our APIs and are currently investigating. This may affect internal API-requests for automatic fronts and…
- Publishing and updating articles
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…
- Security upgrade ResolvedStarted Oct 21, 2026, 01:50 PM UTC · Resolved Oct 21, 2026, 08:17 PM UTC · 6h 26m
- Degraded API performance ResolvedStarted Oct 20, 2026, 11:51 AM UTC · Resolved Oct 20, 2026, 01:13 PM UTC · 1h 21m