NA Data Center: Session Processing Backlog and Partial Data Loss

What to do

• Check whether your product depends on FullStory. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-06-05 16:44 UTC and 2026-05-07 04:00 UTC may need a replay.

• Subscribe to FullStory's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=fullstory works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from FullStory 1

1. resolvedMay 7, 2026, 4:00 AM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.