FullStory: JS API Error
Timeline of updates
- resolved
Some sites using FS.identify experienced exceptions due to a namespacing problem in the JS API. The problem was introduced at 12:00 PM EDT and has been resolved as of 1:15 pm EDT. Please contact support@fullstory.com for questions or additional details.
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 2016-06-01 17:31 UTC, resolved after 0 min, 1 update(s).
- Title
- JS API Error
- Vendor
- FullStory
- Date
- URL
- https://rewindex.com/company/fullstory/incidents/85yk37blpn5k
FullStory profileRecent FullStory incidentsAll outages on June 1, 2016FullStory in June 2016MarkdownJSON