rewindex

CompaniesFullStoryIncidents

FullStory: NA Data Center: Session Processing Backlog and Partial Data Loss

No impact listedStatus: resolvedStarted Resolved (-62551 min)1 updatestspg.io (opens in new tab)

Timeline of updates

  1. resolved

    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 backlog in our database. 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. 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 April 6th, 11:00 UTC to April 14th, 14:00 UTC when the issue was ultimately resolved.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by FullStory, started 2026-05-19 21:31 UTC, resolved after -62551 min, 1 update(s).

Title
NA Data Center: Session Processing Backlog and Partial Data Loss
Vendor
FullStory
Date
URL
https://rewindex.com/company/fullstory/incidents/5wms48wmpl3y

FullStory profileRecent FullStory incidentsAll outages on May 19, 2026FullStory in May 2026MarkdownJSON