FullStory Outage History

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.

This incident in the EU1 region has been resolved. All data processing delays have been cleared, and all systems are now operating normally.

Correction: The issue began at approximately 18:40 ET, not 18:40 UTC as previously stated. We have resolved the issue that was causing delays for our warehouse customers in the EU1 region, and all systems are now fully operational. Our team will continue to ensure all data is processed correctly. We appreciate your patience and apologize for any inconvenience this may have caused.

We experienced a service disruption in our EU1 region that impacted playback functionality from 8:45 AM to 9:37 AM UTC. We apologize for any inconvenience this may have caused.

From 1:04 PM to 1:26 PM EST, Fullstory experienced elevated error rates for session capture and some areas of the app. This also caused slight processing delays that lasted until about 2:00 PM EST. There was minimal to no data loss, and most failed requests were successful on retry.

From January 22, 2026 at 12:54 PM ET through January 23, 2026 at 11:26 AM ET, the Get Session API was unintentionally unavailable. Any requests to Get Session API may have incorrectly responded with HTTP 403 for valid calls. Fullstory customers that attempted to send an API request during the outage window will need to process these requests again. If you believe your account was impacted or have any questions, please reach out to [email protected].

This incident has been resolved.

A fix was released November 13 at 6:10pm (EST) for the GetSegments and ListSegments API issue. All issues are now resolved. During the outage window, any requests to either of these APIs (to retrieve either a list of all segments or information on a specific segment) could have returned incomplete data or otherwise would have returned in an error. For any Fullstory customers that made requests to either endpoint during the outage timeframe, we suggest making the same requests again to ensure you have complete and accurate data about the segment(s) in your Fullstory account. If you have any further questions regarding this issue, please contact us at [email protected].

Our indexing backlog is now fully resolved. Session data captured during the impact window is available for search and in data warehouses.

This incident is now resolved. If you notice any issues with degradation in the Fullstory Web application, please reach out to [email protected].

Search results and display times have now returned to expected levels.

This issue is now resolved. If you notice any further data syncing issues with your warehouse please reach out to [email protected].

We've seen a decrease in errors and Fullstory objects should be returning to normal behavior. We do not expect any further impacts in the coming hours or days and will make changes to prevent these errors from causing such performance impacts in the future.

All backlogged sessions are now indexed. If you notice any persisting issues please reach out to [email protected] for assistance.

We've identified and resolved the issue causing a performance impact to the Fullstory UI. The Fullstory Web Application is now fully operational.

We have implemented a fix that has resolved the issue and our team is still actively investigating the underlying cause to prevent future occurrences. Please reach out to [email protected] if you experience any further issues.

From 6:30am ET until 9:00am ET we were experiencing delays in session processing for accounts in our EU data center. New sessions may not have appeared until 9:30am ET but no data was lost. The issue is now fully resolved and all sessions captured during this time have been processed.

All systems are back to normal operations and are working as expected.

From 10:15 - 10:35am EST today, we identified an issue with logging in to the Fullstory application. This issue has since been resolved and access to Fullstory has been restored. As a result of this issue, there is a slight delay in session processing that will be caught up within 30 - 60 minutes following the resolution.

Things are back to normal now and users should no longer be seeing latency in data loading. If you continue to have issues, please reach out [email protected].

The delays have subsided and this incident is now resolved. Please write into [email protected] if you experience further trouble.