FullStory incident

GetSegments and ListSegments APIs Unavailable

Minor Resolved View vendor source →

FullStory experienced a minor incident on November 12, 2025 affecting API, lasting 1d 5h. The incident has been resolved; the full update timeline is below.

Started
Nov 12, 2025, 06:10 PM UTC
Resolved
Nov 13, 2025, 11:45 PM UTC
Duration
1d 5h
Detected by Pingoru
Nov 12, 2025, 06:10 PM UTC

Affected components

API

Update timeline

  1. identified Nov 12, 2025, 06:10 PM UTC

    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 [email protected].

  2. identified Nov 12, 2025, 11:43 PM UTC

    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 [email protected] for assistance.

  3. identified Nov 13, 2025, 07:23 PM UTC

    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 [email protected] for assistance.

  4. resolved Nov 13, 2025, 11:45 PM UTC

    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 [email protected].