Lessonly incident

Slowness issues for customers in EAST4 region

Major Resolved View vendor source →

Lessonly experienced a major incident on September 30, 2026 affecting U.S. East4, lasting 4h 10m. The incident has been resolved; the full update timeline is below.

Started
Sep 30, 2026, 02:56 PM UTC
Resolved
Sep 30, 2026, 07:06 PM UTC
Duration
4h 10m
Detected by Pingoru
Sep 30, 2026, 02:56 PM UTC

Affected components

U.S. East4

Update timeline

  1. investigating Sep 30, 2026, 02:56 PM UTC

    We are currently investigating this issue.

  2. identified Sep 30, 2026, 03:27 PM UTC

    We have identified the cause of the slowness some customers have experienced, including slow page loads, delays generating LiveDocs and workspaces, and timeouts when publishing content through the API. The cause is an abnormally high volume of automated requests to our Content Manager service. We have stopped the source of the traffic and added capacity to the affected service, and performance is improving but has not yet fully returned to normal. Our teams are continuing to work on the fix and monitor the environment.

  3. monitoring Sep 30, 2026, 03:36 PM UTC

    We have mitigated the slowness and degraded performance that some customers experienced, including slow page loads, delays generating LiveDocs and workspaces, and timeouts when publishing content through the API. The system performance has returned to normal levels. We are continuing to monitor the environment closely, and our teams will conduct a full Root Cause Analysis (RCA) and implement additional safeguards to prevent a recurrence.

  4. resolved Sep 30, 2026, 07:06 PM UTC

    The slowness and degraded performance that some customers experienced beginning has been resolved. Affected areas included slow page loads, delays generating LiveDocs and workspaces, and timeouts when publishing content through the API. Performance returned to normal levels at approximately 8:30 AM PDT and have remained stable since. Our teams will conduct a full Root Cause Analysis (RCA). We apologize for the disruption.