LogRocket

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-07-22 01:00 UTC

   Between 8:50pm and 9:10pm America/New_York on July 21st, there were availability blips during an upgrade of our nginx proxy layer. SDK clients will have retried during this event and we recovered from a backlog by 9:30pm.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Metrics, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-15 15:05 UTC

   We are investigating elevated queue backlogs for our analytics ingestion. Analytics and alerts may be delayed.

2. monitoring 2026-06-15 16:57 UTC

   Latency is returning to normal. We are waiting on our remaining queues to drain.

3. resolved 2026-06-15 18:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-02 05:23 UTC

   We're investigating slow and failing dashboard queries.

2. identified 2026-06-02 05:41 UTC

   We've identified the problem and are rolling out a fix.

3. resolved 2026-06-02 06:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-18 12:19 UTC

   An outage from our upstream CDN provider is causing instability for our dashboard. Data collection is not impacted.

2. monitoring 2025-11-18 13:37 UTC

   Error rates are improving, we're continuing to monitor stability of the system.

3. resolved 2025-11-18 14:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-05 19:43 UTC

   We are investigating instability in our ingestion endpoints.

2. resolved 2025-11-05 22:49 UTC

   This incident is fully resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Alerts

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-14 14:53 UTC

   We are investigating performance issues with our API server causing dashboard instability. Data collection is not impacted.

2. identified 2025-10-14 15:35 UTC

   We have identified the cause of the issue and are deploying a mitigation.

3. resolved 2025-10-14 15:59 UTC

   The performance issue with our API server has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Metrics, Alerts, Streaming Data Export

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-04 16:55 UTC

   We are currently investigating this issue.

2. investigating 2025-08-04 17:56 UTC

   We are continuing to investigate the issue and are working with our vendor to restore service.

3. monitoring 2025-08-04 19:03 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-08-05 02:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection, Slack Integration, Dashboard, GitHub Integration, Intercom Integration, Timeline, Issues, Metrics, Alerts, Streaming Data Export

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-06-12 18:15 UTC

   We are investigating a wide-spread issue with our cloud provider causing ingestion issues and limited access to the dashboard.

2. identified 2025-06-12 19:07 UTC

   GCP is suffering a service outage. Google has opened an incident tracking this issue at https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW#2c2sBHWU84yPDJ8y1ar4

3. monitoring 2025-06-12 20:42 UTC

   The upstream issue has been resolved. We are monitoring and beginning to work through the backlog of session data.

4. monitoring 2025-06-12 20:42 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-06-13 01:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics, Alerts

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-24 19:14 UTC

   We are currently investigating this issue.

2. monitoring 2025-02-24 20:04 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-02-24 21:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-19 18:26 UTC

   We are investigating issues causing ingestion delays. We're working with a vendor to identify the root cause of the problem

2. investigating 2025-02-19 21:24 UTC

   We are continuing to work with a vendor on identifying the root cause of our ingestion delays.

3. monitoring 2025-02-19 23:19 UTC

   We've applied a fix and are monitoring the results

4. resolved 2025-02-20 01:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-02-04 18:29 UTC

   We are investigating issues causing ingestion delays and performance issues loading the dashboard and metrics.

2. investigating 2025-02-04 19:11 UTC

   Dashboard performance should be improved. We are continuing to work with a vendor on identifying the root cause of our ingestion delays.

3. monitoring 2025-02-04 20:38 UTC

   We have identified a potential cause and observing significant improvements to ingestion delays. We are continuing to monitor.

4. resolved 2025-02-04 21:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Streaming Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-01-29 22:04 UTC

   The Streaming Data Export service is delayed. We've identified the issue and are working to remediate.

2. investigating 2025-01-29 22:55 UTC

   We are continuing to investigate this issue.

3. identified 2025-01-30 01:10 UTC

   We've resolved the issue for most Streaming Data Export destinations. A few customers have been temporarily disabled until another fix goes out in the morning, at which time they will be caught up and we will resolve the incident.

4. identified 2025-01-30 21:42 UTC

   We are continuing to work on a fix for this issue.

5. resolved 2025-01-30 21:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection, Dashboard, Timeline, Issues, Metrics, Alerts, Streaming Data Export

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-01-08 15:40 UTC

   We are seeing significant infrastructure instability from our hosting provider.

2. resolved 2025-01-08 16:37 UTC

   The system has stabilized and our processing backlog is recovering.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-06-21 15:00 UTC

   We are investigating instability in our ingestion endpoints.

2. monitoring 2024-06-21 15:57 UTC

   Ingestion has stabilized, we are continuing to monitor the recovery.

3. monitoring 2024-06-21 17:21 UTC

   We are continuing to work down a backlog of ingestion from the initial outage, but have otherwise recovered from the outage.

4. resolved 2024-06-21 18:22 UTC

   The backlog has fully recovered.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Metrics, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-03-30 17:03 UTC

   We've identified an issue with our analytics database resulting in delayed ingestion and degraded alerting performance. The problem has been identified and we're working on a solution.

2. monitoring 2024-03-30 19:38 UTC

   A fix has been implemented and ingestion is recovering

3. resolved 2024-03-30 23:08 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Timeline

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-10-30 20:12 UTC

   We're seeing elevated error rates loading the UI.

2. resolved 2023-10-30 20:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Streaming Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-09-22 16:35 UTC

   Our Streaming Data Export system is not currently exporting data, we are working to resolve this. When this is reenabled it will catch up on data that would have been exported earlier.

2. monitoring 2023-09-22 17:24 UTC

   The most recent export window ran successfully but we're continuing to monitor it for issues.

3. monitoring 2023-09-22 19:59 UTC

   We've monitored several exports and believe this is resolved.

4. resolved 2023-09-22 19:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-16 20:08 UTC

   We are investigating an issue with slow and/or unresponsive application load times.

2. identified 2023-08-16 22:20 UTC

   We've identified the source of the instability and are working through recovery.

3. resolved 2023-08-16 22:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics, Streaming Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-08-09 14:09 UTC

   We are investigating an issue with one of our search databases. Ingestion into this system is currently delayed, and loading data on the dashboard may be slow or timeout. Session Data collection is not impacted.

2. investigating 2023-08-09 17:07 UTC

   We are continuing to investigate this issue.

3. identified 2023-08-09 20:45 UTC

   Our vendor has identified a root cause and we are working to restore the search database to full performance.

4. monitoring 2023-08-09 23:21 UTC

   System performance has been restored. We are continuing to monitor as we work through the remaining backlog of events to process.

5. monitoring 2023-08-10 00:32 UTC

   We are continuing to monitor for any further issues.

6. resolved 2023-08-10 01:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Metrics

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-08 15:01 UTC

   We are investigating an issue with our analytics data stores. Dashboard performance and data freshness may be degraded.

2. identified 2023-08-08 18:49 UTC

   We've stabilized our infrastructure and are beginning to burn down our queues.

3. resolved 2023-08-08 23:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-07-20 22:30 UTC

   We are currently investigating degraded performance of the LogRocket dashboard. Data collection is unaffected

2. identified 2023-07-20 23:06 UTC

   The issue has been identified and a fix is being implemented. Users may experience missing sourcemap uploads as we resolve the issue.

3. resolved 2023-07-21 00:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Metrics, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-07-19 13:56 UTC

   We are currently investigating an issue with secondary search indexing. Data collection and session replay are not impacted.

2. monitoring 2023-07-19 18:42 UTC

   We've worked with our vendor to implement a fix and we're starting to catch up and monitoring systems as we do.

3. resolved 2023-07-19 21:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Metrics, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-07-14 14:10 UTC

   We are currently investigating an issue with secondary search indexing. Data collection and session replay are not impacted.

2. monitoring 2023-07-15 02:25 UTC

   We have addressed the issue and are continuing to monitor the situation. Some secondary search indexing remains delayed at this time.

3. resolved 2023-07-15 03:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Issues, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-06-15 19:01 UTC

   We are investigating an issue with secondary search indexing. Data collection and session replay are not impacted

2. monitoring 2023-06-15 21:05 UTC

   Processing is caught up and stable - we're monitoring to make sure the datastore is stable.

3. resolved 2023-06-15 22:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-05-25 16:25 UTC

   We are investigating an issue with secondary search indexing. Data collection and session replay are not impacted.

2. identified 2023-05-25 17:07 UTC

   We have identified a cause and are working towards a resolution.

3. monitoring 2023-05-25 23:42 UTC

   We have resolved the issue and anticipate the backlog of events to take 1 to to 2 hours to complete.

4. resolved 2023-05-26 01:42 UTC

   The backlog has been completely processed and all systems are now up to date.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-05-10 15:00 UTC

   We are investigating processing delays that impacts a small subset of metrics and filters. Session collection is not impacted, and the majority of metrics and filters are not impacted by the processing delay. We will update as we identify and work to resolve the processing delay.

2. identified 2023-05-10 15:46 UTC

   We have identified an issue causing the performance degradation and are working with a vendor to resolve the issue.

3. identified 2023-05-10 17:03 UTC

   Processing systems are now up-to-date, but we are continuing to investigate and monitor the service causing the original delay.

4. identified 2023-05-10 21:45 UTC

   We are continuing efforts with our vendor to resolve a stability issue with a secondary search database.

5. monitoring 2023-05-10 23:47 UTC

   We are working with our vendor to implement a resolution to our secondary search databases stability issues and expect to have the issue resolved completely in the next few hours.

6. resolved 2023-05-11 12:12 UTC

   After working with our vendor we believe things stabilized overnight. We will be monitoring throughout the day on Thursday.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Issues, Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-03-15 01:11 UTC

   We're investigating ingestion delays in our metrics pipeline.

2. identified 2023-03-15 01:49 UTC

   We've identified the problem and are working on a resolution.

3. resolved 2023-03-15 03:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics, Alerts

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-01-18 15:41 UTC

   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.

2. identified 2023-01-18 16:24 UTC

   We have identified the issue with our database vendor and are working with them to remedy the situation.

3. identified 2023-01-18 18:00 UTC

   We are continuing to work with our vendor to resolve the issue with ingesting new data.

4. identified 2023-01-18 20:02 UTC

   We are continuing to work with our vendor to resolve the issue.

5. identified 2023-01-19 01:00 UTC

   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.

6. identified 2023-01-19 05:03 UTC

   We have restored some indexing to the database but are continuing to fully resolve the situation.

7. monitoring 2023-01-19 08:15 UTC

   We have identified the cause of the issue, applied a fix and have begun processing the backlog of events.

8. monitoring 2023-01-19 15:41 UTC

   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.

9. resolved 2023-01-20 14:00 UTC

   We've seen no additional performance degradation after our mitigation work.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2022-12-08 01:45 UTC

   We are investigating performance and availability issues with our primary search database. This impacts searching for sessions, loading metrics, and ingestion of event data into the search database. Session recording ingestion is not impacted by this performance issue.

2. identified 2022-12-08 03:01 UTC

   We have completed recovery work on the data store and are beginning to backfill search, metrics, and issues data. This process will take several hours to complete and we will continue to monitor the system during that time. No data will be lost. While the backfill is in...

3. resolved 2022-12-08 05:12 UTC

   All systems are functioning normally again.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection, Issues, Metrics, Alerts

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2022-12-05 18:02 UTC

   We have identified the issue with session ingestion and are working to deploy a solution.

2. monitoring 2022-12-05 18:27 UTC

   A fix has been deployed and we're monitoring as session collection catches up.

3. resolved 2022-12-05 18:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2022-11-14 15:20 UTC

   We're experiencing constrained compute availability from our hosting provider. This may affect performance and stability of the user-facing dashboards as our infrastructure prioritizes data collection and integrity. Our team is working to increase capacity.

2. monitoring 2022-11-15 03:28 UTC

   The largest piece of a remediation has been rolled out by our provider. We expect further updates to take time, but believe the most disruptive issue has been resolved.

3. resolved 2022-11-15 21:47 UTC

   We believe the provider issues have been resolved and will be working with them to ensure this does not happen again.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2022-11-13 17:50 UTC

   We are currently investigating an issue where the LogRocket dashboard is not serving requests.

2. monitoring 2022-11-13 18:40 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2022-11-13 21:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2022-10-24 19:59 UTC

   We are working with our vendor to resolve performance issues with our primary search database. The issue is impacting performance of searching for sessions, loading metrics, and ingestion of event data into the search database. Session recording ingestion is not impacted by this...

2. resolved 2022-10-25 01:30 UTC

   We've worked around the issue, and will be performing a larger maintenance overnight but at this time the issue appears to be resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2022-10-18 17:18 UTC

   We are investigating performance issues with our primary search database. The issue is impacting performance of searching for sessions, loading metrics, and ingestion of event data into the search database. Session recording ingestion is not impacted by this performance issue.

2. investigating 2022-10-18 18:33 UTC

   We are continuing to investigate this performance issue with our hosting provider.

3. identified 2022-10-18 20:20 UTC

   We have identified a misbehaving node in our search cluster, our hosting provider is working to repair the node.

4. resolved 2022-10-18 21:09 UTC

   The problematic node has been replaced in our search cluster and performance should be returning to normal levels.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2022-09-28 21:42 UTC

   We are currently investigating this issue.

2. identified 2022-09-29 02:06 UTC

   The issue has been identified and we're working through a processing backlog

3. monitoring 2022-09-29 02:55 UTC

   We're watching the data store as processing is catching up.

4. resolved 2022-09-29 04:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2022-03-30 15:39 UTC

   We are currently investigating an issue with our primary search cluster that is causing delays in processing some search data. Alerting is also impacted at this time. Session ingestion is not impacted and we continue to record new sessions.

2. monitoring 2022-03-30 18:41 UTC

   We've implemented some fixes and are waiting for a backlog to process while monitoring.

3. resolved 2022-03-30 21:48 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection, Alerts

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2022-03-04 18:42 UTC

   We are working with our vendor to investigate an issue with our primary database. Ingestion of new data is currently delayed.

2. monitoring 2022-03-04 19:26 UTC

   Ingestion of new data has recovered. We are continuing to work with our vendor to better understand the failure and monitor for continued success throughout the day.

3. monitoring 2022-03-04 19:28 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2022-03-04 19:45 UTC

   We are continuing to monitor for any further issues- alerting is impacted while we work towards a resolution

5. resolved 2022-03-04 20:44 UTC

   We are continuing to monitor but systems have returned to normal at this time.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard, Issues, Metrics, Alerts

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-12-09 20:03 UTC

   We are currently investigating an issue with our primary search cluster that is causing severe delays in loading the dashboard and searching over sessions. Alerting is also impacted at this time. Session ingestion is not impacted and we continue to record new sessions.

2. monitoring 2021-12-09 21:53 UTC

   We've identified the problem and are working to monitor and stabilize the system before we resolve the issue.

3. resolved 2021-12-10 04:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Issues, Metrics, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2021-12-02 19:20 UTC

   We are investigating an issue with one of our data stores. This is a high-priority issue as we work to resolve the delays impacting Issues, Metrics and Alerts.

2. resolved 2021-12-03 04:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Issues, Metrics, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-10-07 16:14 UTC

   We are investigating an issue with one of our processing pipelines with our hosting provider. This is a high-priority issue as we work to resolve the delays impacting Issues, Metrics and Alerts.

2. resolved 2021-10-07 23:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Issues, Metrics, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2021-10-05 15:27 UTC

   We have identified an issue that is causing delays in our data processing. We will update here when the backlog is cleared.

2. investigating 2021-10-06 13:48 UTC

   The previously identified issue was resolved but has not fully recovered our data processing systems. We have been in contact and continue to work with our upstream provider on this issue.

3. investigating 2021-10-06 13:48 UTC

   We are continuing to investigate this issue.

4. monitoring 2021-10-06 17:33 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2021-10-06 18:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Issues, Metrics, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2021-10-04 14:09 UTC

   We have identified an autoscaling issue that is causing delays in our data processing. We are adding more resources manually, and will update this status when the backlog is cleared.

2. identified 2021-10-04 14:10 UTC

   Updating affected components

3. identified 2021-10-04 14:11 UTC

   Updating affected components

4. resolved 2021-10-05 03:10 UTC

   Delayed data has been reprocessed.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-08-24 16:48 UTC

   We are currently investigating degraded search performance on our dashboards.

2. resolved 2021-08-24 17:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-08-23 19:36 UTC

   We are currently investigating degraded search performance on our dashboards.

2. resolved 2021-08-23 20:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2021-07-12 14:20 UTC

   We received customer reports that our SDK interfered with the popular lodash library, resulting in broken customer sites. We've rolled back to a known functional version of our SDK. The incident lasted for about an hour and 40 minutes.

2. postmortem 2021-07-19 15:49 UTC

   A bug in our build pipeline caused our SDK to expose an internal library globally. As a result, our subset of the lodash library was bound to `window._`, overwriting the existing `_` global for some customer sites. This meant that some expected library functions were not defined...

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-06-03 15:52 UTC

   We are currently investigating an issue with session ingestion.

2. identified 2021-06-03 16:40 UTC

   The issue impacting ingestion has been identified. Session ingestion is currently delayed.

3. monitoring 2021-06-03 16:51 UTC

   A fix has been implemented. We are monitoring closely as we begin to process pending sessions.

4. monitoring 2021-06-03 18:13 UTC

   We are continuing to monitor as we process pending sessions. We expect session ingestion to be real-time within the hour, followed by secondary processing and alerting.

5. identified 2021-06-03 18:59 UTC

   A new issue has been identified and we're working with our vendor to resolve the issue so we can resume processing of delayed sessions.

6. monitoring 2021-06-03 23:09 UTC

   Operations have been restored with our primary search cluster. We have resumed processing of delayed sessions.

7. monitoring 2021-06-04 01:55 UTC

   Primary session processing is now real-time. Secondary processing of session data continues, and will complete over the next hours.

8. resolved 2021-06-04 04:06 UTC

   Systems have remained stable while continuing to process the backlog of events. We estimate secondary processing will be live in the next 6 hours.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Session Collection, Issues, Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-05-05 19:13 UTC

   We are experiencing delays in our data ingestion pipeline. We have identified the issue and are working towards a resolution. No data has been lost and we expect to catch up shortly. Search, metrics, and error reporting are currently delayed.

2. monitoring 2021-05-05 22:15 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2021-05-06 12:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2021-04-20 16:38 UTC

   Our authentication provider is experiencing an outage, preventing authenticating and logging in to our dashboard.

2. resolved 2021-04-20 20:51 UTC

   Dashboard users appear to be able to log in successfully again. We will continue monitoring the incident until our authentication provider reports that all functionality has been restored and provide any relevant updates.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-03-02 13:52 UTC

   We are investigating reports of intermittent errors loading the session list in the LogRocket dashboard.

2. identified 2021-03-02 14:23 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2021-03-02 16:23 UTC

   We have deployed a fix and are monitoring the results

4. resolved 2021-03-02 16:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-02-05 16:22 UTC

   We are currently investigating this issue.

2. resolved 2021-02-06 05:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LogRocket's status page.