- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on FullStory. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide 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 2024-05-07 08:55 UTC and 2024-05-07 04: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
We have investigated and resolved errors received while attempting to log in to or use the web application. Data capture was unaffected, though there were delays in processing data which would affect multiple parts of the application (Session Replay, Metrics, Webhooks, APIs, Destinations).
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-34f37d01c9
Is FullStory still down?
No, this incident was resolved 2024-05-07 04:30 UTC. For FullStory's live state, see https://down.guide/providers/fullstory.
How long did it last?
0m, from 2024-05-07 08:55 UTC to 2024-05-07 04: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.