LogRocket reported this major-impact incident on its official status page on Jan 18, 2023, 15:41 UTC. It was resolved after 1d 22h.
Right now LogRocket is operational. Live LogRocket status →
We've seen no additional performance degradation after our mitigation work.
We have completed processing of our primary indexing backlog, session filtering and metrics will be mostly up-to-date. Our secondary processing system is currently processing and includes some metrics, issues and alerting.
We have identified the cause of the issue, applied a fix and have begun processing the backlog of events.
We have restored some indexing to the database but are continuing to fully resolve the situation.
We are continuing to work with our vendor to remedy the situation. Session data collection continues to be unaffected, but secondary indexing that powers search and metrics continues to be delayed.
We are continuing to work with our vendor to resolve the issue.
We are continuing to work with our vendor to resolve the issue with ingesting new data.
We have identified the issue with our database vendor and are working with them to remedy the situation.
We are currently investigating an issue impacting our primary search database. Searching for sessions, loading metric charts, issues and alerting are all impacted. Session data collection has not been impacted.
Our 5-minute checks didn't record a change in LogRocket's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
LogRocket reported 0 incidents in the last 90 days. See LogRocket's uptime and incident history