在恢复会话时未装入资产( 欧盟1数据中心)
Outage重大事件
- resolved
9月23日对如何解决被捕获资产的URL进行了修改;这无意中导致在欧盟1数据中心的会话中出现回放被打破. 这通过在协调世界时9:45回滚这个变化来固定.
自动翻译自官方事件更新。
58 Fullstory incidents · 2023年11月 — official updates, affected components, duration and resolution details.
9月23日对如何解决被捕获资产的URL进行了修改;这无意中导致在欧盟1数据中心的会话中出现回放被打破. 这通过在协调世界时9:45回滚这个变化来固定.
自动翻译自官方事件更新。
我们针对一个导致某些会议数据提供被拖延、导致搜索和仪表板性能退化以及可能延迟通知的应用软件全程的问题采取了补救措施。 我们正在积极监测结果,以确保充分稳定.
我们正在继续监测任何其他问题.
这一事件现已解决. 若您在下午六点十五分之前遇到任何问题.
自动翻译自官方事件更新。
我们意识到,我们的云基础设施供应商(Google Cloud平台)所报告的一个问题影响到NA1数据中心的多种全程服务。 受影响的服务包括数据捕捉(网络和本地移动)、Fullstory网络应用程序、API、Webhooks & Alerts、任何地方:仓库、指南和调查、SoryAI和劳动力。 数据捕捉可能在此期间被中断. 我们正与我们的提供者积极接触,正在密切监测局势,并将随时提供最新情况.
我们正看到云基础设施提供者(Google Cloud平台)报告的这一问题得到恢复,并正在积极监测,以确保全面稳定地向前迈进。 您也可以在此直接跟踪提供者的状态: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
我国云基础设施提供商(Google Cloud平台)报告的问题现已解决,自2026年9月1日起,全程服务于4:32 PM(ET)全面开通. 目前正在处理任何积压的数据,不久将提供。 如果您有任何问题或持续出现问题, 请联系@fulstory.com.
自动翻译自官方事件更新。
在10:40AM ET上,NA1的Silver Schema用户开始经历仓库同步延迟,所有用户在11:10am ET左右受到影响. 我们仍在调查这一问题.
我们针对这个问题采取了一项措施,开始于10:40AM ET左右,这导致我们在NA1地区的Silver Schema仓库客户延误。 该系统正在赶上。 我们的团队正在采取措施,确保所有数据得到准确处理,一旦所有处理恢复正常,我们将发布另一份更新.
导致NA1地区Silver Schema仓库客户延误的问题已经解决,服务于2026年8月18日4:23 PM ET恢复全面运营. 如果你有任何问题或正在经历任何持续的问题,请毫不犹豫地联系我们的团队@fulstory.com.
自动翻译自官方事件更新。
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.
我们意识到大查询的一个问题始于2026年7月23日早上7点45分左右, 我们正在密切监测局势,并将在获得最新情况后提供最新情况.
为澄清这一事件的范围: Fullstory在内部使用BigQuery来转换所有任何地方的数据:NA1数据中心的仓库客户,无论最终目的地类型如何. 因此,这种大查询退化可能延误了所有地点的少量表格的同步:NA1中的仓库客户——包括大查询,红移,Databricks,和雪花目的地——不仅仅是客户直接同步到大查询. 我们正在继续监测,并将在同步恢复时提供进一步的最新资料.
此事已决. 潜在的大查询退化已经得到缓解,Fullstory用于任何地方的数据转换层:NA1中的仓库已经恢复正常运行. 在此期间延迟的任何同步现在都赶上了,受影响的表格在所有目的地(大查询站、Redshift站、Databricks站和Snowflake站)都是最新的。 这个问题发生在2026年7月23日大约从7:45 AM ET到11:20 AM ET. 我们为干扰道歉,并感谢你的耐心。 如果您继续看到问题, 请用电子邮件通知我们@ fullstory.com .
自动翻译自官方事件更新。
直接嵌入Dashboards,Specle Replay的StoryAI功能背后的模型,由于谷歌的出道而出现退化的可用性. 我们正在同他们的团队密切合作来解决这一问题。 Fullstory中的其他AI功能此时没有受到影响.
这件事已经解决了
自动翻译自官方事件更新。
Between July 6, 2026 at 8:47 AM EDT and July 7, 2026 at 12:00 PM EDT, incorrect filter configurations were intermittently applied to the default canned metrics (Users Today, Sessions Today, Error Rate, and Avg Page Load Time), which could have caused them to display unexpected filter values or report zero results due to no matching data. If you have any questions or are experiencing any continued issues with canned metrics, please reach out to [email protected].
Beginning at approximately 04:00 CEST (22:00 EDT Jun 10), end users on sites where Guides & Surveys is installed may have experienced guides, tours, surveys, and smart tips not displaying correctly, and interaction data was delayed. This 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.
This incident has been resolved. Guides, tours, surveys, and smart tips are now delivering normally for end users in the NA data center. We apologize for the disruption and are implementing additional safeguards to prevent recurrence. If you are still experiencing issues, please contact support at [email protected].
We are investigating an issue where Metric Alerts are triggering at thresholds that do not match the underlying metric data for customers in both our EU and NA data centers. Customers may be receiving alert notifications that appear to fire incorrectly or more frequently than expected. Our engineering team has been notified and is actively investigating. We will provide an update as soon as we have more information. We apologize for the disruption and appreciate your patience.
As of 9:36 AM ET on June 11, 2026, this issue is resolved. A feature flag introduced as part of our multi-metric support rollout caused alert evaluations to diverge from actual metric values, resulting in Metric Alerts firing incorrectly even when the underlying metric had not breached its threshold. Start time of this issue: Multi-Metric Beta customers: June 4, 2026 at 10:27 AM ET All other customers using Metrics with division: June 10, 2026 at 4:25 PM ET If you continue to receive alerts you believe are incorrect, please reach out to us at [email protected]. We apologize for the disruption.
We are monitoring an issue that began on June 6 at 10:00am ET causing data processing delays in our EU1 data center. New sessions are appearing normally, but analytics for recent sessions and data sent from Fullstory to connected warehouses may be delayed. A fix has been implemented today and we are monitoring the system's recovery. We will provide another update as soon as possible.
This issue is now resolved. If you notice any further delays in analytics indexing or data warehouse syncing reach out to [email protected].
On April 6th, 2026, we introduced a limit on the number of pages that can be recorded in a single session to ensure optimal performance. An unexpected side effect caused our systems to continue collecting excess session data without properly saving it, creating a processing backlog. To resolve this, we quickly paused the limit and significantly increased our system's processing capacity to clear the backlog. Unfortunately, because of the size of the delay, a portion of session data was permanently deleted before it could be successfully archived. Due to ongoing metric degradation as a result of that incident, we experienced a similar build up in our processing backlog on May 18th 2026. While we were able to capture the events in these sessions, the affected sessions will appear in a blank state. This issue impacted a small subset of sessions in some customer accounts in our NA data center from May 7th, 04:00 UTC to May 19th, 07:00 UTC when the issue was ultimately resolved.
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.
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.
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.
We are currently experiencing delays in data processing in our EU1 data center. New sessions may not appear until several minutes later. Additionally, data passed to connected warehouses from Fullstory will be delayed. We are investigating the issue.
Our team has implemented a fix and the system is now catching up. We are addressing delays that began at the following times: - Analytics: 2026-02-27 20:00 UTC - Warehouse: 2026-02-25 03:00 UTC We are taking steps to ensure all data is processed accurately and will post another update once processing is back to normal.
The delay in processing for new sessions has been resolved and this system is now operating normally. We are continuing to work through the delays affecting data passed to connected warehouses from Fullstory. We will provide another update once all processing is back to normal.
This incident in the EU1 region has been resolved. All data processing delays have been cleared, and all systems are now operating normally.
We are currently monitoring an issue that is causing delays for warehouse customers located in our EU1 region. Customers may experience slower than normal processing times. We have identified the root cause and will continue to monitor the situation. We will provide another update as soon as we have more information.
We have implemented a fix for the issue that began around 18:40 UTC, which was causing delays for our warehouse customers in the EU1 region. The system is now catching up. Our team is taking steps to ensure all data is processed accurately, and we will post another update once all processing is back to normal.
Correction: The issue began at approximately 18:40 ET, not 18:40 UTC as previously stated. We have resolved the issue that was causing delays for our warehouse customers in the EU1 region, and all systems are now fully operational. Our team will continue to ensure all data is processed correctly. We appreciate your patience and apologize for any inconvenience this may have caused.
We experienced a service disruption in our EU1 region that impacted playback functionality from 8:45 AM to 9:37 AM UTC. We apologize for any inconvenience this may have caused.
From 1:04 PM to 1:26 PM EST, Fullstory experienced elevated error rates for session capture and some areas of the app. This also caused slight processing delays that lasted until about 2:00 PM EST. There was minimal to no data loss, and most failed requests were successful on retry.
From January 22, 2026 at 12:54 PM ET through January 23, 2026 at 11:26 AM ET, the Get Session API was unintentionally unavailable. Any requests to Get Session API may have incorrectly responded with HTTP 403 for valid calls. Fullstory customers that attempted to send an API request during the outage window will need to process these requests again. If you believe your account was impacted or have any questions, please reach out to [email protected].
Certain organizations are experiencing elevated server API error rates, specifically for the create event batch API.
This incident has been resolved.