FullStory: Temporary Recording Failure
Timeline of updates
- resolved
On September 18, 2019, between 6:03 PM and 6:41 PM EDT (2019-09-19 00:03 - 00:41 UTC), FullStory recording experienced increased error rates that impacted the majority of recording requests. For recordings that would have occurred during this time, session playback will likely be completely or partially unavailable. The incident started when a critical, replicated database service became unavailable and our system failed to compensate for this service being down. While we expect this database service to be highly reliable, we’re exploring options to mitigate future incidents should this service be unavailable in the future. If you have any questions or concerns regarding this incident and how it may have affected your FullStory account, feel free to reach out to us at 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 2019-09-18 22:03 UTC, resolved after 0 min, 1 update(s).
- Title
- Temporary Recording Failure
- Vendor
- FullStory
- Date
- URL
- https://rewindex.com/company/fullstory/incidents/2ykhrgk34wcp
FullStory profileRecent FullStory incidentsAll outages on September 18, 2019FullStory in September 2019MarkdownJSON