Labrador CMS incident

Service disruptions

Resolved after 30 minutes, affecting Labrador Editor and Labrador Frontend, on April 28, 2025.

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.

Started
Apr 28, 2025, 11:49 AM UTC
Resolved
Apr 28, 2025, 12:19 PM UTC
Duration
30m
Detected by Pingoru
Apr 28, 2025, 11:49 AM UTC

Affected components

Labrador EditorLabrador Frontend

Update timeline

  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.

Your product runs on more than Labrador CMS

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →