- Level
- confirmed
- Worst impact
- Degraded
- Components
- Fullstory Web Application
- Down Index
- 21of 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 3h 35m it lasted.
Anything that failed between 2025-03-14 17:09 UTC and 2025-03-14 20:45 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 4
- identified
At 12:44am EST today, we noticed users experiencing slow loading or failure to load Fullstory. We are actively investigating the issue.
provider
- monitoring
We’ve identified a slow query that was leading to degraded performance. We are implementing the necessary changes to guard against future performance degradation. Fullstory should be back up and running. Please reach out to support@fullstory.com with any further issues/questions
provider
- monitoring
We have identified the root cause but out of an abundance of caution are planning to implement a fix on Monday. Our teams will monitor in the meantime and, should there be any further issues, they will be quickly addressed. When our fix is implemented on Monday we’ll provide another status update, or by 12:00pm EDT at the latest. If you experience any issues prior to Monday, please reach out to support@fullstory.com for assistance.
provider
- resolved
After careful consideration, we have made changes on our end and this incident is now resolved. Please write into support@fullstory.com if you experience further trouble.
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-2b31e92219
Is FullStory still down?
No, this incident was resolved 2025-03-14 20:45 UTC. For FullStory's live state, see https://down.guide/fullstory.
How long did it last?
3h 35m, from 2025-03-14 17:09 UTC to 2025-03-14 20:45 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.