Historial de interrupciones de Fullstory

1. August 18, 2026 at 5:57 PM UTCinvestigating

   A las 10:40AM ET, los usuarios de Silver Schema en NA1 comenzaron a experimentar retrasos de sincronización de almacén con todos los usuarios afectados alrededor de 11:10am ET. Todavía estamos investigando este tema.

2. August 18, 2026 at 6:42 PM UTCmonitoring

   Hemos implementado una solución para el tema que comenzó alrededor de 10:40AM ET, que estaba causando retrasos para nuestros clientes de almacén de Silver Schema en la región de NA1. El sistema se está poniendo al día. Nuestro equipo está tomando medidas para asegurar que todos los datos se procesan con precisión, y publicaremos otra actualización una vez que todo el procesamiento vuelva a la normalidad.

3. August 18, 2026 at 8:24 PM UTCresolved

   El problema que causó retrasos para los clientes de los almacenes de Silver Schema en la región de NA1 ha sido resuelto y el servicio está de vuelta al pleno funcionamiento a partir del 18 de agosto de 2026 a las 4:23 PM ET. Si tiene alguna pregunta o está experimentando problemas continuos, no dude en contactar con nuestro equipo en [email protected].

Traducido automáticamente desde la actualización oficial del incidente.

1. August 7, 2026 at 1:40 PM UTCresolved

   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.

1. July 23, 2026 at 3:46 PM UTCmonitoring

   Somos conscientes de un problema con BigQuery que comenzó alrededor del 23 de julio de 2026 a las 7:45 AM (ET) que está impactando Fullstory en cualquier lugar: conexiones de almacén utilizando BigQuery. Estamos monitoreando de cerca la situación y proporcionaremos actualizaciones cuando estén disponibles.

2. July 23, 2026 at 5:16 PM UTCmonitoring

   Para aclarar el alcance de este incidente: Fullstory utiliza BigQuery internamente para transformar datos para todos los lugares: Clientes de almacén en el centro de datos NA1, independientemente del tipo de destino final. Como resultado, esta degradación de BigQuery puede haber retrasado la sincronización de un pequeño número de tablas para todos los lugares: Clientes de almacén en NA1 — incluyendo BigQuery, Redshift, Databricks y destinos de Snowflake— no sólo los clientes se sincronizan directamente con BigQuery. Seguimos monitoreando y proporcionaremos otra actualización a medida que se recuperen los sincronizados.

3. July 23, 2026 at 8:58 PM UTCresolved

   Este incidente está resuelto. La degradación subyacente de BigQuery ha sido mitigada, y la capa de transformación de datos que Fullstory utiliza para cualquier lugar: Warehouse en NA1 ha vuelto a la operación normal. Cualquier sincronización que se haya retrasado durante este período ya se ha captado, y las tablas afectadas están al día en todos los destinos (BigQuery, Redshift, Databricks y Snowflake). El tema ocurrió de aproximadamente 7:45 AM ET a 11:20 AM ET el 23 de julio de 2026. Nos disculpamos por la interrupción y gracias por su paciencia. Envíenos un correo electrónico a [email protected] si continúa viendo problemas.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 16, 2026 at 8:38 PM UTCinvestigating

   El modelo detrás de las características de StoryAI que están directamente incrustadas dentro de Dashboards, Segments y Session Replay están viendo disponibilidad degradada debido a un outage de Google. Trabajamos estrechamente con su equipo para resolver este problema. Otras características de IA dentro de Fullstory no son impactadas en este momento.

2. July 16, 2026 at 10:41 PM UTCresolved

   Este incidente se ha resuelto

Traducido automáticamente desde la actualización oficial del incidente.

1. July 8, 2026 at 8:15 PM UTCresolved

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

1. June 11, 2026 at 1:58 PM UTCmonitoring

   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 data center. 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. June 11, 2026 at 5:08 PM UTCresolved

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

1. June 11, 2026 at 1:28 PM UTCinvestigating

   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. June 11, 2026 at 4:45 PM UTCresolved

   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.

1. June 8, 2026 at 5:15 PM UTCmonitoring

   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. June 8, 2026 at 6:05 PM UTCresolved

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

1. June 5, 2026 at 4:44 PM UTCresolved

   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.

1. May 19, 2026 at 9:31 PM UTCresolved

   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.

1. March 17, 2026 at 7:19 PM UTCresolved

   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. March 17, 2026 at 7:19 PM UTCpostmortem

   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.

1. February 27, 2026 at 9:53 PM UTCinvestigating

   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. February 28, 2026 at 12:14 AM UTCmonitoring

   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. February 28, 2026 at 12:52 AM UTCmonitoring

   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. February 28, 2026 at 4:23 AM UTCresolved

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

1. February 25, 2026 at 4:20 PM UTCmonitoring

   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. February 25, 2026 at 7:36 PM UTCmonitoring

   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. February 25, 2026 at 10:06 PM UTCresolved

   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.

1. February 18, 2026 at 9:55 AM UTCresolved

   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.

1. February 13, 2026 at 8:54 PM UTCresolved

   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.

1. January 23, 2026 at 5:09 PM UTCresolved

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

1. December 19, 2025 at 5:19 PM UTCinvestigating

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

2. December 19, 2025 at 8:09 PM UTCresolved

   This incident has been resolved.

1. November 18, 2025 at 8:32 PM UTCinvestigating

   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. November 18, 2025 at 9:23 PM UTCmonitoring

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

3. November 18, 2025 at 9:47 PM UTCresolved

   This incident has been resolved.

1. November 12, 2025 at 6:10 PM UTCidentified

   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. November 12, 2025 at 11:43 PM UTCidentified

   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. November 13, 2025 at 7:23 PM UTCidentified

   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. November 13, 2025 at 11:45 PM UTCresolved

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

1. October 29, 2025 at 5:59 PM UTCinvestigating

   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. October 29, 2025 at 10:00 PM UTCidentified

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

3. October 30, 2025 at 11:42 AM UTCmonitoring

   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. October 30, 2025 at 12:30 PM UTCresolved

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