Is FullStory down?

We are aware of an issue with BigQuery that started around July 23, 2026 at 7:45 AM (ET) which is impacting Fullstory Anywhere: Warehouse connections utilising BigQuery. We are closely monitoring the situation and will provide updates as they become available.

To clarify the scope of this incident: Fullstory uses BigQuery internally to transform data for all Anywhere: Warehouse customers in the NA1 data center, regardless of the final destination type. As a result, this BigQuery degradation may have delayed the sync of a small number of tables for all Anywhere: Warehouse customers in NA1 — including BigQuery, Redshift, Databricks, and Snowflake destinations — not only customers syncing directly to BigQuery. We are continuing to monitor and will provide a further update as syncs recover.

This incident is resolved. The underlying BigQuery degradation has been mitigated, and the data transformation layer that Fullstory uses for Anywhere: Warehouse in NA1 has returned to normal operation. Any syncs that were delayed during this period have now caught up, and affected tables are up to date across all destinations (BigQuery, Redshift, Databricks, and Snowflake). The issue occurred from approximately 7:45 AM ET to 11:20 AM ET on July 23, 2026. We apologize for the disruption and thank you for your patience. Email us at [email protected] if you continue to see issues.

The model behind the StoryAI features that are directly embedded within Dashboards, Segments, and Session Replay are seeing degraded availability due to a Google outage. We are working closely with their team to resolve this issue. Other AI features within Fullstory are not impacted at this time.

This incident has been resolved

Between July 6, 2026 at 8:47 AM EDT and July 7, 2026 at 12:00 PM EDT, incorrect filter configurations were intermittently applied to the default canned metrics (Users Today, Sessions Today, Error Rate, and Avg Page Load Time), which could have caused them to display unexpected filter values or report zero results due to no matching data. If you have any questions or are experiencing any continued issues with canned metrics, please reach out to [email protected].

Beginning at approximately 04:00 CEST (22:00 EDT Jun 10), end users on sites where Guides & Surveys is installed may have experienced guides, tours, surveys, and smart tips not displaying correctly, and interaction data was delayed. This issue was caused by resource exhaustion in the service responsible for delivering and recording end-user activity, not in the FullStory application itself. The FullStory app, Guides & Surveys editor, and theme/targeting configuration were not affected. No data was lost. Content delivery may have been delayed, and whether queued interactions are replayed will depend on whether the end user's session re-qualifies against targeting rules. We have identified the root cause of this issue, implemented a fix, and are actively monitoring the service. We will provide a further update once the service has been fully restored.

This incident has been resolved. Guides, tours, surveys, and smart tips are now delivering normally for end users in the NA data center. We apologize for the disruption and are implementing additional safeguards to prevent recurrence. If you are still experiencing issues, please contact support at [email protected].

We are investigating an issue where Metric Alerts are triggering at thresholds that do not match the underlying metric data for customers in both our EU and NA data centers. Customers may be receiving alert notifications that appear to fire incorrectly or more frequently than expected. Our engineering team has been notified and is actively investigating. We will provide an update as soon as we have more information. We apologize for the disruption and appreciate your patience.

As of 9:36 AM ET on June 11, 2026, this issue is resolved. A feature flag introduced as part of our multi-metric support rollout caused alert evaluations to diverge from actual metric values, resulting in Metric Alerts firing incorrectly even when the underlying metric had not breached its threshold. Start time of this issue: Multi-Metric Beta customers: June 4, 2026 at 10:27 AM ET All other customers using Metrics with division: June 10, 2026 at 4:25 PM ET If you continue to receive alerts you believe are incorrect, please reach out to us at [email protected]. We apologize for the disruption.