FullStory Outage History

Started Sep 23, 2026, 07:00 PM UTC· resolved Sep 23, 2026, 07:00 PM UTC

1. resolved Sep 24, 2026, 10:29 AM UTC

   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.

Read the full incident report →

Started Sep 07, 2026, 10:03 PM UTC· resolved Sep 07, 2026, 10:03 PM UTC

1. resolved Sep 07, 2026, 10:03 PM 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.

Read the full incident report →

Started Sep 01, 2026, 03:19 PM UTC· resolved Sep 01, 2026, 08:36 PM UTC

1. investigating Sep 01, 2026, 03:19 PM UTC

   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.

2. monitoring Sep 01, 2026, 04:32 PM UTC

   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

3. resolved Sep 01, 2026, 08:36 PM UTC

   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].

Read the full incident report →

Started Aug 18, 2026, 05:57 PM UTC· resolved Aug 18, 2026, 08:24 PM UTC

1. investigating Aug 18, 2026, 05:57 PM UTC

   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.

2. monitoring Aug 18, 2026, 06:42 PM UTC

   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.

3. resolved Aug 18, 2026, 08:24 PM UTC

   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].

Read the full incident report →

Started Aug 06, 2026, 07:00 PM UTC· resolved Aug 07, 2026, 08:30 AM UTC

1. resolved Aug 07, 2026, 01:40 PM UTC

   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.

Read the full incident report →

Started Jul 23, 2026, 03:46 PM UTC· resolved Jul 23, 2026, 08:58 PM UTC

1. monitoring Jul 23, 2026, 03:46 PM UTC

   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.

2. monitoring Jul 23, 2026, 05:16 PM UTC

   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.

3. resolved Jul 23, 2026, 08:58 PM UTC

   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.

Read the full incident report →

Started Jul 16, 2026, 08:38 PM UTC· resolved Jul 16, 2026, 10:41 PM UTC

1. investigating Jul 16, 2026, 08:38 PM UTC

   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.

2. resolved Jul 16, 2026, 10:41 PM UTC

   This incident has been resolved

Read the full incident report →

Started Jul 06, 2026, 12:30 PM UTC· resolved Jul 06, 2026, 04:00 PM UTC

1. resolved Jul 08, 2026, 08:15 PM UTC

   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].

Read the full incident report →

Started Jun 11, 2026, 01:58 PM UTC· resolved Jun 11, 2026, 05:08 PM UTC

1. monitoring Jun 11, 2026, 01:58 PM UTC

   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.

2. resolved Jun 11, 2026, 05:08 PM UTC

   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].

Read the full incident report →

Started Jun 11, 2026, 01:28 PM UTC· resolved Jun 11, 2026, 04:45 PM UTC

1. investigating Jun 11, 2026, 01:28 PM UTC

   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.

2. resolved Jun 11, 2026, 04:45 PM UTC

   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.

Read the full incident report →

Started Jun 08, 2026, 05:15 PM UTC· resolved Jun 08, 2026, 06:05 PM UTC

1. monitoring Jun 08, 2026, 05:15 PM UTC

   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.

2. resolved Jun 08, 2026, 06:05 PM UTC

   This issue is now resolved. If you notice any further delays in analytics indexing or data warehouse syncing reach out to [email protected].

Read the full incident report →

Started May 07, 2026, 04:00 AM UTC· resolved May 07, 2026, 07:00 AM UTC

1. resolved Jun 05, 2026, 04:44 PM 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.

Read the full incident report →

Started Mar 17, 2026, 07:19 PM UTC· resolved Mar 17, 2026, 07:19 PM UTC

1. resolved Mar 17, 2026, 07: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.

2. postmortem Mar 17, 2026, 07: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 [[email protected]](mailto:[email protected]). We stand by ready to fully address all of your concerns.

Read the full incident report →

Started Feb 27, 2026, 09:53 PM UTC· resolved Feb 28, 2026, 04:23 AM UTC

1. investigating Feb 27, 2026, 09:53 PM UTC

   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.

2. monitoring Feb 28, 2026, 12:14 AM UTC

   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.

3. monitoring Feb 28, 2026, 12:52 AM UTC

   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.

4. resolved Feb 28, 2026, 04:23 AM UTC

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

Read the full incident report →

Started Feb 25, 2026, 04:20 PM UTC· resolved Feb 25, 2026, 10:06 PM UTC

1. monitoring Feb 25, 2026, 04:20 PM UTC

   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.

2. monitoring Feb 25, 2026, 07:36 PM UTC

   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.

3. resolved Feb 25, 2026, 10:06 PM UTC

   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.

Read the full incident report →

Started Feb 18, 2026, 08:45 AM UTC· resolved Feb 18, 2026, 09:37 AM UTC

1. resolved Feb 18, 2026, 09:55 AM UTC

   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.

Read the full incident report →

Started Feb 13, 2026, 06:04 PM UTC· resolved Feb 13, 2026, 07:00 PM UTC

1. resolved Feb 13, 2026, 08:54 PM UTC

   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.

Read the full incident report →

Started Jan 22, 2026, 05:00 PM UTC· resolved Jan 22, 2026, 05:00 PM UTC

1. resolved Jan 23, 2026, 05:09 PM UTC

   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].

Read the full incident report →

Started Dec 19, 2025, 05:19 PM UTC· resolved Dec 19, 2025, 08:09 PM UTC

1. investigating Dec 19, 2025, 05:19 PM UTC

   Certain organizations are experiencing elevated server API error rates, specifically for the create event batch API.

2. resolved Dec 19, 2025, 08:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 12, 2025, 06:10 PM UTC· resolved Nov 13, 2025, 11:45 PM UTC

1. identified Nov 12, 2025, 06:10 PM UTC

   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].

2. identified Nov 12, 2025, 11:43 PM UTC

   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.

3. identified Nov 13, 2025, 07:23 PM UTC

   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.

4. resolved Nov 13, 2025, 11:45 PM UTC

   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].

Read the full incident report →

Started Oct 29, 2025, 05:59 PM UTC· resolved Oct 30, 2025, 12:30 PM UTC

1. investigating Oct 29, 2025, 05:59 PM UTC

   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.

2. identified Oct 29, 2025, 10:00 PM UTC

   We've identified the issue and we're working to rectify it at this time.

3. monitoring Oct 30, 2025, 11:42 AM UTC

   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.

4. resolved Oct 30, 2025, 12:30 PM UTC

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

Read the full incident report →

Started Oct 22, 2025, 07:42 PM UTC· resolved Oct 22, 2025, 09:35 PM UTC

1. identified Oct 22, 2025, 07:42 PM UTC

   Customers may have experienced delayed data processing and indexing, or degradation to the Fullstory Web application between 2:46 PM ET to 2:55 PM ET. Data ingested within this timeframe may be delayed or affected. We have identified the issue and are actively working on full resolution.

2. resolved Oct 22, 2025, 09:35 PM UTC

   This issue is resolved. The Fullstory platform, including login, data processing and indexing, webhooks, APIs, and destinations, are fully operational. If there are any follow up questions, please reach out to [email protected].

3. postmortem Oct 23, 2025, 10:13 PM UTC

   2025/10/22 Fullstory Networking Disruption On October 22, 2025, the Fullstory platform experienced a 30-minute networking control plane partial outage, beginning at 2:44 PM EDT. This incident led to widespread degradation, impacting network requests for many applications and resulting in customer logouts, partial capture failure, and delayed indexing and warehousing sync. The root cause was identified as a misconfiguration of resource pinning within a component of Fullstory's central networking infrastructure. This misconfiguration prevented the component from restarting successfully after an update, leading to a cycle of crashing and restarting as the remaining service replicas became overloaded. # Customer Impact During the incident window, some API requests, Fullstory Analytics app usage, and data captures would have resulted in HTTP errors. Some users logged into Fullstory Analytics were logged out of the application. Affected sessions will have missing data causing gaps/disruptions when loading playback, webhooks not firing, and events not being exported via the Anywhere: Warehouse feature. Data capture may have been affected for all orgs during the incident window. Please reach out to [[email protected]](mailto:[email protected]) if you have any questions or concerns. # Root Cause Due to an update in configuration, our networking control plane required a progressive restart. Normally this restart happens very quickly without effect on any systems. Due to an unforeseen misconfiguration of resource pinning, the control plane spiked in CPU and caused a domino effect on itself, unable to recover without intervention. # Resolution After receiving alerts on the failed networking components, our Core Infrastructure team took action to quickly implement changes to stop the cascading failures. These interventions were strategically designed to prevent a cascading series of failures across our interconnected systems, thereby mitigating further impact and providing a rapid restoration of services. # Process Changes and Prevention **Actions Taken:** * Stabilized the core networking components * Added resiliency to these components to better handle full load during replica loss * Fixed misconfiguration of resource pinning to allow networking components to fully utilize all available resources ‌ We deeply regret this incident and invite any Fullstory customer who was materially affected to contact [[email protected]](mailto:[email protected]). We stand by ready to fully address all of your concerns.

Read the full incident report →

Started Oct 20, 2025, 08:11 PM UTC· resolved Oct 21, 2025, 12:32 PM UTC

1. investigating Oct 20, 2025, 08:11 PM UTC

   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.

2. investigating Oct 20, 2025, 09:52 PM UTC

   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.

3. monitoring Oct 21, 2025, 12:07 AM UTC

   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.

4. resolved Oct 21, 2025, 12:32 PM UTC

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

Read the full incident report →

Started Aug 27, 2025, 08:38 AM UTC· resolved Aug 27, 2025, 03:55 PM UTC

1. investigating Aug 27, 2025, 08:38 AM UTC

   As of approximately 7am UTC, we are experiencing an elevated error rate displaying data in app for a subset of orgs (EU1 Data Center). Metrics, Segments, Funnels, and Dashboards may be slow to load. They may timeout with an error. Data capture is not affected. We are actively investigating the issue and will update this status as soon as we know more.

2. monitoring Aug 27, 2025, 08:49 AM UTC

   A fix has been implemented and we are monitoring the results.

3. investigating Aug 27, 2025, 09:06 AM UTC

   We are still experiencing an elevated error rate displaying data . We are actively investigating the issue and will update this status as soon as we know more.

4. monitoring Aug 27, 2025, 09:40 AM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Aug 27, 2025, 03:55 PM UTC

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

Read the full incident report →

Started Aug 13, 2025, 09:35 PM UTC· resolved Aug 14, 2025, 06:26 PM UTC

1. identified Aug 13, 2025, 09:35 PM UTC

   Warehouse syncs and updates are delayed starting at 4:41PM ET for customers in an NA environment. We're working to identify the issue and address it accordingly.

2. monitoring Aug 14, 2025, 01:09 PM UTC

   We've identified the root cause of this issue. Data is now being sent to warehouses but syncing may be delayed as we work through the backlog.

3. resolved Aug 14, 2025, 06:26 PM UTC

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

Read the full incident report →