- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Regions
- us
- Down Index
- 27of 100
What to do
Check whether you use FullStory API in us. 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 1d 5h it lasted.
Anything that failed between 2025-11-12 18:10 UTC and 2025-11-13 23: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
From October 27, 2025 at 11:37am (EDT) to November 7, 2025 at 11:12am (EST), the datastores which serve our GetSegments and ListSegments APIs were unintentionally no longer updated. Requests made to these endpoints during this timeframe may have not returned complete data. Starting November 7 at 11:12am (EST), requests to these APIs began returning an error. We are currently identifying the appropriate resolution and will continue to provide updates on progress. If you believe your account was impacted or have any questions, please reach out to support@fullstory.com.
provider
- identified
We are continuting to work towards a resolution to restore full functionality and complete data for the GetSegments and ListSegments APIs. We'll provide another update by 3:00pm (EST) tomorrow after further work and testing has been done. If you have any questions regarding this issue prior to our next update, please reach out to support@fullstory.com for assistance.
provider
- identified
We have identified a solution for the GetSegments and ListSegments API issue and are implementing a fix. We will provide an update once the fix is released. If you have any questions regarding this issue prior to our next update, please reach out to support@fullstory.com for assistance.
provider
- resolved
A fix was released November 13 at 6:10pm (EST) for the GetSegments and ListSegments API issue. All issues are now resolved. During the outage window, any requests to either of these APIs (to retrieve either a list of all segments or information on a specific segment) could have returned incomplete data or otherwise would have returned in an error. For any Fullstory customers that made requests to either endpoint during the outage timeframe, we suggest making the same requests again to ensure you have complete and accurate data about the segment(s) in your Fullstory account. If you have any further questions regarding this issue, please contact us at 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-ca59c8728d
Is FullStory still down?
No, this incident was resolved 2025-11-13 23:45 UTC. For FullStory's live state, see https://down.guide/fullstory.
How long did it last?
1d 5h, from 2025-11-12 18:10 UTC to 2025-11-13 23:45 UTC, by the times FullStory posted.
What was affected?
FullStory named API in us.
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.