Skip to main content
FullStory

Anywhere: Warehouse - Delayed data syncs in NA1 Data Center

Degraded Lasted 5h 12m · started · FullStory's page

Level
confirmed
Worst impact
Degraded
Components
Anywhere: Warehouse
Regions
us
Down Index
25of 100

What to do

  • Check whether you use FullStory Anywhere: Warehouse in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 5h 12m it lasted.

    Anything that failed between 2026-07-23 15:46 UTC and 2026-07-23 20:58 UTC may need a replay.
  • Subscribe to FullStory's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=fullstory works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from FullStory 3

  1. monitoring

    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.

    provider

  2. monitoring

    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.

    provider

  3. resolved

    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 support@fullstory.com if you continue to see issues.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-15839542c7

Is FullStory still down?

No, this incident was resolved 2026-07-23 20:58 UTC. For FullStory's live state, see https://down.guide/fullstory.

How long did it last?

5h 12m, from 2026-07-23 15:46 UTC to 2026-07-23 20:58 UTC, by the times FullStory posted.

What was affected?

FullStory named Anywhere: Warehouse in us.

What caused it?

FullStory hasn't published a root cause. If it does, it shows here.

Where does this come from?

FullStory's official status page, https://status.fullstory.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.