- Level
- confirmed
- Worst impact
- Degraded
- Components
- Anywhere: Warehouse
- Down Index
- 24of 100
What to do
Check whether you use FullStory Anywhere: Warehouse. 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 20h 51m it lasted.
Anything that failed between 2025-08-13 21:35 UTC and 2025-08-14 18:26 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
- identified
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.
provider
- monitoring
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.
provider
- resolved
This issue is now resolved. If you notice any further data syncing issues with your warehouse please reach out to support@fullstory.com.
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-f1ce774763
Is FullStory still down?
No, this incident was resolved 2025-08-14 18:26 UTC. For FullStory's live state, see https://down.guide/fullstory.
How long did it last?
20h 51m, from 2025-08-13 21:35 UTC to 2025-08-14 18:26 UTC, by the times FullStory posted.
What was affected?
FullStory named Anywhere: Warehouse.
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.