Data transport to data warehouse significantly delayed for some customers

What to do

• Check whether you use FullStory Anywhere: Warehouse, Anywhere: Warehouse. 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-03-17 19:19 UTC and 2026-03-17 19:19 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 2

1. resolvedMar 17, 2026, 7:19 PM UTC

   Some customers using Fullstory Anywhere: Warehouse may have observed a significant decrease in the number of events being transported to their data warehouse between February 24, 2026 to March 13, 2026. No data was lost during this time and all data has been backfilled to the impacted customers' warehouses. This incident is now resolved.

   provider

2. postmortemMar 17, 2026, 7:19 PM UTC

   2026/02/24 Data transport to data warehouse significantly delayed for some customers This postmortem details the customer impact, the root cause of what happened, how we addressed the problem, and how we will prevent it from happening in the future. # Customer Impact Some customers using Fullstory Anywhere: Warehouse may have observed a significant decrease in the number of events being transported to their data warehouse between Feb 24, 2026 to Mar 13, 2026. The impact here is limited to object storage destinations such as Amazon S3, Azure Blob Storage, and Google Cloud Storage. # Root Cause The Fullstory platform has two internal pipelines that generate event data and notify downstream systems. There is a streaming pipeline for real time event processing, and a batch pipeline for everything else. Object storage data destinations receive notifications from the latter whenever it processes session and page entities that are deemed inactive i.e. no longer receiving event data. On Feb 24, 2026 the team made a change to the streaming pipeline to track additional metadata about page entities that were being processed. Unfortunately this change had an unintended effect on the batch pipeline which caused notifications to not be fired upon successful processing for a subset of events. Thus event data that should have been transported to object storage to instead remain buffered indefinitely. # Resolution On Mar 11, 2026 the team investigated the issue and pinpointed it to a code change that was deployed on Feb 24, 2026. A fix was deployed on the same day as the issue was found. From there events from newly processed page entities began flowing to affected customer’s data warehouses again. Once the fix was in place the team focused on impact analysis and remediation. A backfill process was kicked off on Mar 12, 2026 to transport event data that did not originally make it to affected customer’s data warehouses. As of Mar 13, 2026 the backfill is complete and any gaps in event data have been filled. No further action is required from those impacted. # Process Changes and Prevention Our team has completed a thorough review of the incident, fixed the relevant bug, and implemented a backfill process for remediation here. We have also identified several areas of improvement with our metrics and monitoring, as well as system changes to prevent this kind of unintended cross-pipeline impact. We deeply regret this incident and invite any Fullstory customer who was materially affected to contact [support@fullstory.com](mailto:support@fullstory.com). We stand by ready to fully address all of your concerns.

   provider

Corrections

None so far.

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