FullStory

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-09-23 19:00 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 sessions in the EU1 Data Center. This was fixed by rolling back this change at 9:45am UTC.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application, Webhooks & Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-07 15:00 UTC

   We have implemented a fix for an issue that 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...

2. monitoring 2026-09-07 22:34 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-09-08 05:46 UTC

   This incident has now been resolved. If you are experiencing any issues past 6:15 PM (ET), please email us at support@fullstory.com.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Data Capture - Web, Data Capture - Native Mobile, API, Fullstory Web Application, Fullstory Web Application, Webhooks & Alerts, Anywhere: Warehouse, Guides and Surveys, StoryAI, Workforce

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. investigating 2026-09-01 15:19 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,...

2. monitoring 2026-09-01 16:32 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:...

3. resolved 2026-09-01 20:36 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application, Fullstory Web Application, Webhooks & Alerts, Webhooks & Alerts, Anywhere: Warehouse, Anywhere: Warehouse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-18 17:57 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 2026-08-18 18:42 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...

3. resolved 2026-08-18 20:24 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-06 19:00 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....

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Anywhere: Warehouse

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-07-23 15:46 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 2026-07-23 17:16 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...

3. resolved 2026-07-23 20:58 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: StoryAI

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-16 20:38 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...

2. resolved 2026-07-16 22:41 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-06 12:30 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Guides and Surveys

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-06-11 13:58 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 only is impacting customers in our NA...

2. resolved 2026-06-11 17:08 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Webhooks & Alerts, Webhooks & Alerts

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-11 13:28 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...

2. resolved 2026-06-11 16:45 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application, Anywhere: Warehouse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-08 17:15 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...

2. resolved 2026-06-08 18:05 UTC

   This issue is now resolved. If you notice any further delays in analytics indexing or data warehouse syncing reach out to support@fulltory.com.

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-07 04:00 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-04-06 11:00 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 backlog in our...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Anywhere: Warehouse, Anywhere: Warehouse

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure, Google Cloud.

1. resolved 2026-03-17 19:19 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...

2. postmortem 2026-03-17 19:19 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Data Capture - Web, Data Capture - Native Mobile, Anywhere: Warehouse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-27 21:53 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 2026-02-28 00:14 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...

3. monitoring 2026-02-28 00:52 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 2026-02-28 04:23 UTC

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

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Anywhere: Warehouse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-02-25 16:20 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...

2. monitoring 2026-02-25 19:36 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...

3. resolved 2026-02-25 22:06 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-02-18 09:55 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.

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-02-13 20:54 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-22 17:00 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-19 17:19 UTC

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

2. resolved 2025-12-19 20:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-18 20:32 UTC

   We are currently experiencing delays processing sessions for accounts utilizing our EU data center. Session capture is not impacted but new sessions may not appear until several minutes after initial capture. We are actively investigating the issue.

2. monitoring 2025-11-18 21:23 UTC

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

3. resolved 2025-11-18 21:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-12 18:10 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....

2. identified 2025-11-12 23:43 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...

3. identified 2025-11-13 19:23 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 support@fullstory.com for...

4. resolved 2025-11-13 23:45 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application, Webhooks & Alerts, Anywhere: Warehouse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-29 17:59 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 2025-10-29 22:00 UTC

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

3. monitoring 2025-10-30 11:42 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 2025-10-30 12:30 UTC

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

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Data Capture - Web, Data Capture - Native Mobile, API, Fullstory Web Application, Anywhere: Warehouse

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-10-22 19:42 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...

2. resolved 2025-10-22 21:35 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 support@fullstory.com.

3. postmortem 2025-10-23 22:13 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...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-20 20:11 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 2025-10-20 21:52 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 2025-10-21 00:07 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 2025-10-21 12:32 UTC

   This incident is now resolved. If you notice any issues with degradation in the Fullstory Web application, please reach out to support@fullstory.com.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-27 08:38 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...

2. monitoring 2025-08-27 08:49 UTC

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

3. investigating 2025-08-27 09:06 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 2025-08-27 09:40 UTC

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

5. resolved 2025-08-27 15:55 UTC

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

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Anywhere: Warehouse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-08-13 21:35 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 2025-08-14 13:09 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 2025-08-14 18:26 UTC

   This issue is now resolved. If you notice any further data syncing issues with your warehouse please reach out to support@fullstory.com.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Data Capture - Native Mobile

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-07-17 09:08 UTC

   We are currently investigating an issue with mobile capture for EU orgs.

2. identified 2025-07-17 09:11 UTC

   An issue was identified with mobile capture for EU orgs. We have determined the cause and rolled back the change that resulted in this issue.

3. monitoring 2025-07-17 09:52 UTC

   An issue was identified with mobile capture for EU orgs. A fix has been implemented and we are now monitoring.

4. resolved 2025-07-17 09:58 UTC

   An issue was identified with mobile capture for EU orgs. This incident has now been resolved.

5. postmortem 2025-07-18 17:14 UTC

   # Postmortem From Wednesday July 16, 8:05 PM UTC through Thursday July 17, 09:42 AM UTC an update to the Native Mobile asset upload service caused 50-70% of all asset management requests to fail due to an issue in routing requests for `rs.eu1.fullstory.com` and...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-14 12:51 UTC

   Yesterday at 10:00pm EDT, we began experiencing an elevated error rate displaying data in app for a subset of orgs (NA1 Data Center). Metrics, Segments, Funnels, and Dashboards may be slow to load. They may timeout with an error. Configured alerts may be delayed. Data capture is...

2. resolved 2025-07-14 14:37 UTC

   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.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-06-12 18:21 UTC

   We are currently investigating a site outage which is impacting logging in and loading the Fullstory UI. We are actively working to identify the root cause and will provide regular updates as they are available.

2. identified 2025-06-12 18:57 UTC

   This outage is due to a current GCP incident that we are closely monitoring here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW#RP1d9aZLNFZEJmTBk8e1 We'll continue to make updates as we evaluate the full impact that this outage has on Fullstory customers.

3. monitoring 2025-06-12 21:02 UTC

   The GCP incident is resolved and we're actively monitoring the results. Sessions captured during the outage are being indexed, but may not yet be available. We'll provide a final update on impact as soon as this is available.

4. resolved 2025-06-13 01:36 UTC

   All backlogged sessions are now indexed. If you notice any persisting issues please reach out to support@fullstory.com for assistance.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-05 15:47 UTC

   We are currently experiencing delays in loading in the Fullstory Web Application. The issue started around 10:25am ET. We are actively investigating the issue and will provide an update as soon as possible.

2. resolved 2025-06-05 16:11 UTC

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

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Data Capture - Web, Data Capture - Native Mobile, Fullstory Web Application

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-18 20:29 UTC

   At 4:19pm ET, we noticed users experiencing slow loading or failure to load Fullstory. We are rolling back recent changes and continuing to investigate and fully resolve this issue.

2. investigating 2025-03-18 21:13 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-03-18 22:09 UTC

   At 4:11 PM EDT, we detected an issue that resulted in degraded performance on Fullstory. The service has been restored, and we are actively investigating the root cause. We will provide further updates as our investigation progresses. If you encounter any additional issues or...

4. resolved 2025-03-19 00:09 UTC

   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 support@fullstory.com if you experience any further issues.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-03-14 17:09 UTC

   At 12:44am EST today, we noticed users experiencing slow loading or failure to load Fullstory. We are actively investigating the issue.

2. monitoring 2025-03-14 17:59 UTC

   We’ve identified a slow query that was leading to degraded performance. We are implementing the necessary changes to guard against future performance degradation. Fullstory should be back up and running. Please reach out to support@fullstory.com with any further issues/questions

3. monitoring 2025-03-14 20:05 UTC

   We have identified the root cause but out of an abundance of caution are planning to implement a fix on Monday. Our teams will monitor in the meantime and, should there be any further issues, they will be quickly addressed. When our fix is implemented on Monday we’ll provide...

4. resolved 2025-03-14 20:45 UTC

   After careful consideration, we have made changes on our end and this incident is now resolved. Please write into support@fullstory.com if you experience further trouble.

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-03-02 11:30 UTC

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

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-02-20 21:05 UTC

   We are currently investigating a Fullstory web application outage for some users. Note: This outage does not affect session capture.

2. monitoring 2025-02-20 21:13 UTC

   We've rolled back some changes that caused this outage and Fullstory should be back up and running again. Please reach out to support@fullstory.com with any further issues/questions.

3. resolved 2025-02-20 21:22 UTC

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

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Data Capture - Web

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-02-12 22:26 UTC

   We are currently experiencing delays in session processing and indexing that began at 4:00pm ET. There may be a delay in your ability to view newly captured sessions. We are investigating the issue.

2. resolved 2025-02-12 23:25 UTC

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

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-01-08 15:35 UTC

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

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-12-11 16:42 UTC

   We are experiencing an elevated latency for data loading for a subset of orgs. Users may receive errors while attempting to load Dashboards, Metrics, and Segments. Some pages may take longer than normal to appear.

2. identified 2024-12-11 21:03 UTC

   We are continuing to work on a fix for the elevated data display latency. Thanks for your patience.

3. resolved 2024-12-11 23:10 UTC

   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 support@fullstory.com.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application, Webhooks & Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-12-10 21:30 UTC

   We are experiencing an elevated error rate displaying data in app for a subset of orgs. Charts may be slow to load. They may timeout with an error. Data capture is not affected. Segment alerts are also delayed for all orgs. We are actively investigating the issue.

2. resolved 2024-12-10 23:34 UTC

   The delays have subsided and this incident is now resolved. Please write into support@fullstory.com if you experience further trouble.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Data Capture - Web, Data Capture - Native Mobile, Fullstory Web Application

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2024-11-14 00:11 UTC

   Our team has identified an issue impacting data capture for web and mobile sessions that started October 31st, 2024 at 4:03pm ET. This issue impacted 4,770 Fullstory accounts, but only impacts about .5% of total captured sessions per account. Due to our internal retention...

2. resolved 2024-11-14 22:12 UTC

   This issue is now resolved. Most accounts will notice a small percentage of sessions affected by this issue. This would result in entirely missing sessions, or pages in sessions, which would also impact Search, Conversions, Metrics, Funnels, and Dashboards. We’re actively...

3. postmortem 2024-12-10 21:16 UTC

   # Postmortem 2024/11/13 Failed Tasks Not Retried / Pages Not Initialized On October 31st, 2024, an issue introduced in our service caused a small percentage \(< 0.05%\) of sessions to not process a portion of data within them. This data was effectively “stuck” in our system. The...

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-10-31 18:30 UTC

   From October 31, 2024 at 2:38PM ET through October 31, 2024 at 4:07PM ET, the Fullstory APIs were unintentionally unavailable. The majority of requests to Fullstory APIs would have returned an error. Fullstory customers that attempted to send an API request during the outage...

2. postmortem 2024-11-07 21:07 UTC

   On October 31, 2024, our API service experienced a disruption that resulted in a significant number of dropped requests and errors. The incident lasted for approximately 1.5 hours and impacted all users of our public server API. # Customer Impact Most public server API requests...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-09-12 20:02 UTC

   Starting on March 26th, as a result of processing optimization improvements, a bug was introduced that resulted in some server events for some accounts not being properly indexed or sent to data warehouses. We were made aware of this issue on September 11th and released a fix on...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application, Webhooks & Alerts, Anywhere: Warehouse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-08-08 17:28 UTC

   We are currently experiencing indexing delays for sessions and Data Warehouse updates in our NA1 data center. We are investigating the issue.

2. monitoring 2024-08-08 17:54 UTC

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

3. resolved 2024-08-08 21:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-05-16 22:30 UTC

   For a period of 40 minutes starting from May 16 11:25 PM UTC, Fullstory customers experienced an elevated rate of errors in the web application. This is related to networking issues in our infrastructure; application availability has returned to normal and is being monitored by...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Data Capture - Web, Data Capture - Native Mobile, Fullstory Web Application

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-05-10 15:38 UTC

   At 10:23 AM ET, we detected login issues and partial data capture outage for web and native mobile. Login issues were resolved by 10:54 AM ET. However, the partial capture outage is ongoing and our team is actively investigating. We'll be sure to update you as soon as we have...

2. monitoring 2024-05-10 16:59 UTC

   We've applied a fix and we're monitoring the results.

3. resolved 2024-05-10 19:53 UTC

   Partial Capture Outage - Web & Mobile: For web and mobile traffic captured between 10:50 AM ET to 12:50 PM ET, there will be delayed processing. Additionally, there may be missing sessions, as well as sessions with missing activity, which could impact Session Playback, Search,...

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-05-08 19:18 UTC

   At approximately 2:10 PM ET today, we began experiencing application delays affecting search and dashboard results. Our team is actively investigating this. We appreciate your patience and will provide updates as we make progress.

2. monitoring 2024-05-08 19:54 UTC

   A fix has been implemented and we're monitoring the results.

3. resolved 2024-05-08 20:22 UTC

   This incident has been resolved. If you continue to experience any issues, please reach out to support@fullstory.com for assistance.

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-05-07 04:30 UTC

   We have investigated and resolved errors received while attempting to log in to or use the web application. Data capture was unaffected, though there were delays in processing data which would affect multiple parts of the application (Session Replay, Metrics, Webhooks, APIs,...

Excerpts are shortened. Read the full incident on FullStory's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-05-06 22:30 UTC

   On Monday, May 6th, 2024 between 6:45pm and 12:30am ET, there was a data processing delay that affected results showing up in the web application or warehouses. Any delays are now fully processed and available.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Anywhere: Warehouse

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-29 21:40 UTC

   We are experiencing some disruption to the data pipeline that powers Data Direct warehousing. We are currently working to resolve the issue.

2. monitoring 2024-04-30 00:31 UTC

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

3. resolved 2024-04-30 13:02 UTC

   This issue has been resolved and all data has been successfully backfilled. If you notice any further disruptions to your data pipeline please reach out to support@fullstory.com.

Excerpts are shortened. Read the full incident on FullStory's status page.

Affected: Fullstory Web Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-22 13:40 UTC

   We are experiencing an elevated error rate for searches and session indexing. Users may receive errors while attempting to load session lists (e.g. "Failed to load user list.") and new sessions may take longer than normal to appear.

2. investigating 2024-04-22 15:04 UTC

   App queries and overall responsiveness have improved. Users should no longer see errors or slow loading. While impact has been mitigated, we are still investigating cause.

3. monitoring 2024-04-22 15:19 UTC

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

4. resolved 2024-04-22 15:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on FullStory's status page.