- 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 2024-10-31 21:33 UTC and 2024-10-31 18: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 2
- resolved
From October 31, 2024 at 2:38PM ET through October 31, 2024 at 4:07PM ET, the Fullstory APIs were unintentionally unavailable. The majority of requests to Fullstory APIs would have returned an error. 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
- postmortem
On October 31, 2024, our API service experienced a disruption that resulted in a significant number of dropped requests and errors. The incident lasted for approximately 1.5 hours and impacted all users of our public server API. # Customer Impact Most public server API requests sent during the incident time frame \(18:37:29 UTC to 20:12:39 UTC\) were unsuccessful and should be re-submitted. We acknowledge the inconvenience and disruption this caused our customers and sincerely apologize for any impact on your operations. # Root Cause The root cause of the incident was a decrease in the capacity of our API service due to an unsuccessful deployment. This decrease in capacity, combined with higher than usual request volume, led to the service being unable to handle the incoming traffic. # Resolution Upon discovery of the issue, our on-call operations team was immediately notified and responded swiftly. The team's actions included re-executing the failed deployment to restore normal API service functionality. # Process Changes and Prevention **Actions Taken:** * We re-executed the unsuccessful deployment. * We permanently scaled up the capacity of our API service to handle the increased traffic. * We are implementing additional monitoring and alerting to detect and prevent similar issues in the future. **Ongoing Improvements:** * We are reviewing our deployment processes to minimize the risk of similar incidents. * We are investigating ways to improve the resilience of our API service to handle unexpected spikes in traffic. We deeply regret this incident and invite any Fullstory customer who was materially affected to contact [support@fullstory.com](mailto:support@fullstory.com). We stand by ready to fully address all of your concerns.
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-c13cc060cb
Is FullStory still down?
No, this incident was resolved 2024-10-31 18:30 UTC. For FullStory's live state, see https://down.guide/fullstory.
How long did it last?
0m, from 2024-10-31 21:33 UTC to 2024-10-31 18: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.