- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
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-07-08 20:15 UTC and 2026-07-06 12:30 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
Between July 6, 2026 at 8:47 AM EDT and July 7, 2026 at 12:00 PM EDT, incorrect filter configurations were intermittently applied to the default canned metrics (Users Today, Sessions Today, Error Rate, and Avg Page Load Time), which could have caused them to display unexpected filter values or report zero results due to no matching data. If you have any questions or are experiencing any continued issues with canned metrics, 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-fa2f30f513
Is FullStory still down?
No, this incident was resolved 2026-07-06 12:30 UTC. For FullStory's live state, see https://down.guide/fullstory.
How long did it last?
0m, from 2026-07-08 20:15 UTC to 2026-07-06 12:30 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.