FullStory incident

NA Data Center: Session Processing Backlog and Partial Data Loss

Notice Resolved View vendor source →

FullStory experienced a notice incident on June 5, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jun 05, 2026, 04:44 PM UTC
Resolved
May 07, 2026, 04:00 AM UTC
Duration
Detected by Pingoru
Jun 05, 2026, 04:44 PM UTC

Update timeline

  1. resolved Jun 05, 2026, 04:44 PM UTC

    On April 6th, 2026, we introduced a limit on the number of pages that can be recorded in a single session to ensure optimal performance. An unexpected side effect caused our systems to continue collecting excess session data without properly saving it, creating a processing backlog. To resolve this, we quickly paused the limit and significantly increased our system's processing capacity to clear the backlog. Unfortunately, because of the size of the delay, a portion of session data was permanently deleted before it could be successfully archived. Due to ongoing metric degradation as a result of that incident, we experienced a similar build up in our processing backlog on May 18th 2026. While we were able to capture the events in these sessions, the affected sessions will appear in a blank state. This issue impacted a small subset of sessions in some customer accounts in our NA data center from May 7th, 04:00 UTC to May 19th, 07:00 UTC when the issue was ultimately resolved.