- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
What to do
Check whether you use FullStory in eu. 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-01-23 17:09 UTC and 2026-01-22 17: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
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 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-a449e5fa5d
Is FullStory still down?
No, this incident was resolved 2026-01-22 17:00 UTC. For FullStory's live state, see https://down.guide/fullstory.
How long did it last?
0m, from 2026-01-23 17:09 UTC to 2026-01-22 17:00 UTC, by the times FullStory posted.
What was affected?
FullStory named in eu.
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.