- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Fullstory Web Application
- Down Index
- 26of 100
What to do
Check whether you use FullStory Fullstory Web Application. 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 17m it lasted.
Anything that failed between 2025-02-20 21:05 UTC and 2025-02-20 21:22 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
- investigating
We are currently investigating a Fullstory web application outage for some users. Note: This outage does not affect session capture.
provider
- monitoring
We've rolled back some changes that caused this outage and Fullstory should be back up and running again. Please reach out to support@fullstory.com with any further issues/questions.
provider
- resolved
All systems are back to normal operations and are working as expected.
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-b4da2dc13b
Is FullStory still down?
No, this incident was resolved 2025-02-20 21:22 UTC. For FullStory's live state, see https://down.guide/fullstory.
How long did it last?
17m, from 2025-02-20 21:05 UTC to 2025-02-20 21:22 UTC, by the times FullStory posted.
What was affected?
FullStory named Fullstory Web Application.
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.