- Level
- confirmed
- Worst impact
- Partial outage
What to do
Check whether your product depends on FullStory. 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 0m it lasted.
Anything that failed between 2026-09-23 19:00 UTC and 2026-09-23 19:00 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 1
- resolved
A change was made on the 23rd of September to how URLs for captured assets are resolved; this inadvertently led to playback being broken for sessions in the EU1 Data Center. This was fixed by rolling back this change at 9:45am UTC.
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-b8ee135b0c
Is FullStory still down?
No, this incident was resolved 2026-09-23 19:00 UTC. For FullStory's live state, see https://down.guide/fullstory.
How long did it last?
0m, from 2026-09-23 19:00 UTC to 2026-09-23 19:00 UTC, by the times FullStory posted.
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.