LogRocket: Session data ingestion issue
Timeline of updates
- resolved
From 11:11AM EDT to 11:15AM EDT our session collection system had an elevated error. This issue was caused by a configuration error when changing over to a new ingestion hostname at r.lr-ingest.io. We have since switched the SDK back to the original ingest host (r.logrocket.io) while we investigate the configuration issue. During this 4 minute period the SDK on customer computers will have continued to collect and attempt to send data to our ingestion service, and the majority of sessions continued to record properly. Customers may have seen elevated bandwidth usage from our SDK during this period as it continued to try and send data through the system.
From LogRocket’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.logrocket.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by LogRocket, started 2019-05-03 15:15 UTC, resolved after 0 min, 1 update(s).
- Title
- Session data ingestion issue
- Vendor
- LogRocket
- Date
- URL
- https://rewindex.com/company/logrocket/incidents/vn6gpxd1vybl
LogRocket profileRecent LogRocket incidentsAll outages on May 3, 2019LogRocket in May 2019MarkdownJSON