FullStory: Server Event Processing Issue
Timeline of updates
- resolved
We didn’t properly ingest server event data from Jan 11, 2024 through Jan 19, 2024 and as a result data processing was delayed across all customers, meaning that custom events sent during the incident period would not appear in FullStory search, sessions, etc. or Data Destinations. Our engineers worked to restore as much of this data as possible. Due to the delay, some associated event context (e.g. timestamps, location, screen size, etc.) was lost. Any customers that had webhooks tied to custom events would not have received those webhooks during this incident. If you have any questions regarding this incident, please reach out to support@fullstory.com.
From FullStory’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.fullstory.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by FullStory, started 2024-01-11 05:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Server Event Processing Issue
- Vendor
- FullStory
- Date
- URL
- https://rewindex.com/company/fullstory/incidents/0dppss5lkn69
FullStory profileRecent FullStory incidentsAll outages on January 11, 2024FullStory in January 2024MarkdownJSON