FullStory had 23 outages in the last 2 years totaling 103h 42m of downtime — averaging 0.9 incidents per month.
There were 23 FullStory outages since October 20, 2025 totaling 103h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.
A change was made on the 23rd of September to how URLs for captured assets are resolved; this inadvertently led to playback being broken for mobile sessions in the EU1 Data Center. This was fixed by rolling back this change at 9:45am UTC.
We have implemented a fix for an issue that’s caused delays in some session data availability, contributed to degraded search and dashboard performance, and potentially delayed alert notifications in Fullstory the application. We are actively monitoring the results to ensure full stability.
We are aware of an issue reported by our cloud infrastructure provider (Google Cloud Platform) impacting multiple Fullstory services in the NA1 data center. Affected services include data capture (web and native mobile), the Fullstory web application, API, Webhooks & Alerts, Anywhere: Warehouse, Guides and Surveys, StoryAI, and Workforce. Data capture may be interrupted during this period. We are actively engaged with our provider, are closely monitoring the situation, and will provide updates as they become available.
We are seeing recovery for the issue reported by our cloud infrastructure provider (Google Cloud Platform) and are actively monitoring to ensure full stability moving forward. You can also follow the provider's status directly here: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
The issue reported by our cloud infrastructure provider (Google Cloud Platform) is now resolved and Fullstory services are fully operational as of September 1st, 2026 at 4:32 PM (ET). Any backlogged data is currently being processed and will be available shortly. If you have any questions or are experiencing any continued issues, please reach out to [email protected].
At 10:40AM ET, Silver Schema users in NA1 began experiencing warehouse sync delays with all users affected around 11:10am ET. We are still investigating this issue.
We have implemented a fix for the issue that began around 10:40AM ET, which was causing delays for our Silver Schema warehouse customers in the NA1 region. The system is now catching up. Our team is taking steps to ensure all data is processed accurately, and we will post another update once all processing is back to normal.
The issue that caused delays for Silver Schema warehouse customers in the NA1 region has been resolved and service is back to full operation as of August 18th, 2026 at 4:23 PM ET. If you have any questions or are experiencing any continued issues, please don't hesitate to reach out to our team at [email protected].
From 7:58pm UTC on the 6th of August, users in NA1 & EU1 organisations with Guides & Surveys enabled were unable to create or edit tours and smart tips. There was also some disruption of end-user content delivery, though this was mitigated by edge caching serving cached content. The issue was resolved by 8:30am UTC on the 7th of August.
We are aware of an issue with BigQuery that started around July 23, 2026 at 7:45 AM (ET) which is impacting Fullstory Anywhere: Warehouse connections utilising BigQuery. We are closely monitoring the situation and will provide updates as they become available.
To clarify the scope of this incident: Fullstory uses BigQuery internally to transform data for all Anywhere: Warehouse customers in the NA1 data center, regardless of the final destination type. As a result, this BigQuery degradation may have delayed the sync of a small number of tables for all Anywhere: Warehouse customers in NA1 — including BigQuery, Redshift, Databricks, and Snowflake destinations — not only customers syncing directly to BigQuery. We are continuing to monitor and will provide a further update as syncs recover.
This incident is resolved. The underlying BigQuery degradation has been mitigated, and the data transformation layer that Fullstory uses for Anywhere: Warehouse in NA1 has returned to normal operation. Any syncs that were delayed during this period have now caught up, and affected tables are up to date across all destinations (BigQuery, Redshift, Databricks, and Snowflake). The issue occurred from approximately 7:45 AM ET to 11:20 AM ET on July 23, 2026. We apologize for the disruption and thank you for your patience. Email us at [email protected] if you continue to see issues.
The model behind the StoryAI features that are directly embedded within Dashboards, Segments, and Session Replay are seeing degraded availability due to a Google outage. We are working closely with their team to resolve this issue. Other AI features within Fullstory are not impacted at this time.
This incident has been resolved
Between July 6, 2026 at 8:47 AM EDT and July 7, 2026 at 12:00 PM EDT, incorrect filter configurations were intermittently applied to the default canned metrics (Users Today, Sessions Today, Error Rate, and Avg Page Load Time), which could have caused them to display unexpected filter values or report zero results due to no matching data. If you have any questions or are experiencing any continued issues with canned metrics, please reach out to [email protected].
Beginning at approximately 04:00 CEST (22:00 EDT Jun 10), end users on sites where Guides & Surveys is installed may have experienced guides, tours, surveys, and smart tips not displaying correctly, and interaction data was delayed. This issue was caused by resource exhaustion in the service responsible for delivering and recording end-user activity, not in the FullStory application itself. The FullStory app, Guides & Surveys editor, and theme/targeting configuration were not affected. No data was lost. Content delivery may have been delayed, and whether queued interactions are replayed will depend on whether the end user's session re-qualifies against targeting rules. We have identified the root cause of this issue, implemented a fix, and are actively monitoring the service. We will provide a further update once the service has been fully restored.
This incident has been resolved. Guides, tours, surveys, and smart tips are now delivering normally for end users in the NA data center. We apologize for the disruption and are implementing additional safeguards to prevent recurrence. If you are still experiencing issues, please contact support at [email protected].
We are investigating an issue where Metric Alerts are triggering at thresholds that do not match the underlying metric data for customers in both our EU and NA data centers. Customers may be receiving alert notifications that appear to fire incorrectly or more frequently than expected. Our engineering team has been notified and is actively investigating. We will provide an update as soon as we have more information. We apologize for the disruption and appreciate your patience.
As of 9:36 AM ET on June 11, 2026, this issue is resolved. A feature flag introduced as part of our multi-metric support rollout caused alert evaluations to diverge from actual metric values, resulting in Metric Alerts firing incorrectly even when the underlying metric had not breached its threshold. Start time of this issue: Multi-Metric Beta customers: June 4, 2026 at 10:27 AM ET All other customers using Metrics with division: June 10, 2026 at 4:25 PM ET If you continue to receive alerts you believe are incorrect, please reach out to us at [email protected]. We apologize for the disruption.
We are monitoring an issue that began on June 6 at 10:00am ET causing data processing delays in our EU1 data center. New sessions are appearing normally, but analytics for recent sessions and data sent from Fullstory to connected warehouses may be delayed. A fix has been implemented today and we are monitoring the system's recovery. We will provide another update as soon as possible.
This issue is now resolved. If you notice any further delays in analytics indexing or data warehouse syncing reach out to [email protected].
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.
We are currently experiencing delays in data processing in our EU1 data center. New sessions may not appear until several minutes later. Additionally, data passed to connected warehouses from Fullstory will be delayed. We are investigating the issue.
Our team has implemented a fix and the system is now catching up. We are addressing delays that began at the following times: - Analytics: 2026-02-27 20:00 UTC - Warehouse: 2026-02-25 03:00 UTC We are taking steps to ensure all data is processed accurately and will post another update once processing is back to normal.
The delay in processing for new sessions has been resolved and this system is now operating normally. We are continuing to work through the delays affecting data passed to connected warehouses from Fullstory. We will provide another update once all processing is back to normal.
This incident in the EU1 region has been resolved. All data processing delays have been cleared, and all systems are now operating normally.
We are currently monitoring an issue that is causing delays for warehouse customers located in our EU1 region. Customers may experience slower than normal processing times. We have identified the root cause and will continue to monitor the situation. We will provide another update as soon as we have more information.
We have implemented a fix for the issue that began around 18:40 UTC, which was causing delays for our warehouse customers in the EU1 region. The system is now catching up. Our team is taking steps to ensure all data is processed accurately, and we will post another update once all processing is back to normal.
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].
Certain organizations are experiencing elevated server API error rates, specifically for the create event batch API.
This incident has been resolved.
From October 27, 2025 at 11:37am (EDT) to November 7, 2025 at 11:12am (EST), the datastores which serve our GetSegments and ListSegments APIs were unintentionally no longer updated. Requests made to these endpoints during this timeframe may have not returned complete data. Starting November 7 at 11:12am (EST), requests to these APIs began returning an error. We are currently identifying the appropriate resolution and will continue to provide updates on progress. If you believe your account was impacted or have any questions, please reach out to [email protected].
We are continuting to work towards a resolution to restore full functionality and complete data for the GetSegments and ListSegments APIs. We'll provide another update by 3:00pm (EST) tomorrow after further work and testing has been done. If you have any questions regarding this issue prior to our next update, please reach out to [email protected] for assistance.
We have identified a solution for the GetSegments and ListSegments API issue and are implementing a fix. We will provide an update once the fix is released. If you have any questions regarding this issue prior to our next update, please reach out to [email protected] for assistance.
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].
At 11:15 AM EDT, we began experiencing indexing delays for session data and Data Warehouse updates in our NA data center. We are investigating the issue.
We've identified the issue and we're working to rectify it at this time.
A fix has been implemented and new session data is no longer delayed. We are monitoring the backlog of session data impacted by these delays and will resolve this incident once the backlogged session data is fully indexed.
Our indexing backlog is now fully resolved. Session data captured during the impact window is available for search and in data warehouses.
Some customers may experience degradation in the Fullstory Web application for some features, and delayed indexing under some circumstances. Both NA and EU data regions appear to be affected. We are actively investigating the issue.
We have identified the issue and our systems have caught up on delayed indexing. We are continuing to work on implementing a full resolution for degradation in the Fullstory Web app for some features.
All issues with indexing and degradation in the Fullstory Web application have been resolved. We are monitoring these results and we will provide another status update by 10:00am ET tomorrow morning.
This incident is now resolved. If you notice any issues with degradation in the Fullstory Web application, please reach out to [email protected].