Logrocket 中断历史

1. 2026年10月24日 UTC 16:12investigating

   我们正在调查我们分析摄入系统 排出更多排队的积压.

2. 2026年10月24日 UTC 18:07monitoring

   我们已经清除了瓶颈,排队排出排出.

3. 2026年10月24日 UTC 19:51resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月22日 UTC 01:31resolved

   8:50pm到9:10pm美洲/New York于7月21日更新Nginx代理层时出现可用blip. SDK客户将在活动期间重新测试,我们从积压中恢复到晚上9: 30.

自动翻译自官方事件更新。

1. 2026年6月15日 UTC 15:05identified

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

2. 2026年6月15日 UTC 16:57monitoring

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

3. 2026年6月15日 UTC 18:21resolved

   This incident has been resolved.

1. 2026年6月2日 UTC 05:23investigating

   We're investigating slow and failing dashboard queries.

2. 2026年6月2日 UTC 05:41identified

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

3. 2026年6月2日 UTC 06:10resolved

   This incident has been resolved.

1. 2025年11月18日 UTC 12:19identified

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

2. 2025年11月18日 UTC 13:37monitoring

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

3. 2025年11月18日 UTC 14:52resolved

   This incident has been resolved.

1. 2025年11月5日 UTC 19:43investigating

   We are investigating instability in our ingestion endpoints.

2. 2025年11月5日 UTC 22:49resolved

   This incident is fully resolved.

1. 2025年10月14日 UTC 14:53investigating

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

2. 2025年10月14日 UTC 15:35identified

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

3. 2025年10月14日 UTC 15:59resolved

   The performance issue with our API server has been resolved.

1. 2025年8月4日 UTC 16:55investigating

   We are currently investigating this issue.

2. 2025年8月4日 UTC 17:56investigating

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

3. 2025年8月4日 UTC 19:03monitoring

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

4. 2025年8月5日 UTC 02:06resolved

   This incident has been resolved.

1. 2025年6月12日 UTC 18:15investigating

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

2. 2025年6月12日 UTC 19:07identified

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

3. 2025年6月12日 UTC 20:42monitoring

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

4. 2025年6月12日 UTC 20:42monitoring

   We are continuing to monitor for any further issues.

5. 2025年6月13日 UTC 01:18resolved

   This incident has been resolved.

1. 2025年2月24日 UTC 19:14investigating

   We are currently investigating this issue.

2. 2025年2月24日 UTC 20:04monitoring

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

3. 2025年2月24日 UTC 21:32resolved

   This incident has been resolved.

1. 2025年2月19日 UTC 18:26investigating

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

2. 2025年2月19日 UTC 21:24investigating

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

3. 2025年2月19日 UTC 23:19monitoring

   We've applied a fix and are monitoring the results

4. 2025年2月20日 UTC 01:35resolved

   This incident has been resolved.

1. 2025年2月4日 UTC 18:29investigating

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

2. 2025年2月4日 UTC 19:11investigating

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

3. 2025年2月4日 UTC 20:38monitoring

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

4. 2025年2月4日 UTC 21:14resolved

   This incident has been resolved.

1. 2025年1月29日 UTC 22:04investigating

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

2. 2025年1月29日 UTC 22:55investigating

   We are continuing to investigate this issue.

3. 2025年1月30日 UTC 01:10identified

   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. 2025年1月30日 UTC 21:42identified

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

5. 2025年1月30日 UTC 21:45resolved

   This incident has been resolved.

1. 2025年1月8日 UTC 15:40investigating

   We are seeing significant infrastructure instability from our hosting provider.

2. 2025年1月8日 UTC 16:37resolved

   The system has stabilized and our processing backlog is recovering.

1. 2024年6月21日 UTC 15:00investigating

   We are investigating instability in our ingestion endpoints.

2. 2024年6月21日 UTC 15:57monitoring

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

3. 2024年6月21日 UTC 17:21monitoring

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

4. 2024年6月21日 UTC 18:22resolved

   The backlog has fully recovered.

1. 2024年3月30日 UTC 17:03identified

   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. 2024年3月30日 UTC 19:38monitoring

   A fix has been implemented and ingestion is recovering

3. 2024年3月30日 UTC 23:08resolved

   This incident has been resolved

1. 2023年10月30日 UTC 20:12investigating

   We're seeing elevated error rates loading the UI.

2. 2023年10月30日 UTC 20:25resolved

   This incident has been resolved.

1. 2023年9月22日 UTC 16:35identified

   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. 2023年9月22日 UTC 17:24monitoring

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

3. 2023年9月22日 UTC 19:59monitoring

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

4. 2023年9月22日 UTC 19:59resolved

   This incident has been resolved.

1. 2023年8月16日 UTC 20:08investigating

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

2. 2023年8月16日 UTC 22:20identified

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

3. 2023年8月16日 UTC 22:35resolved

   This incident has been resolved.

1. 2023年8月9日 UTC 14:09investigating

   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. 2023年8月9日 UTC 17:07investigating

   We are continuing to investigate this issue.

3. 2023年8月9日 UTC 20:45identified

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

4. 2023年8月9日 UTC 23:21monitoring

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

5. 2023年8月10日 UTC 00:32monitoring

   We are continuing to monitor for any further issues.

6. 2023年8月10日 UTC 01:13resolved

   This incident has been resolved.