有辱人格的数据收集
- investigating
我们目前正在调查一个影响部分客户的日志摄入的问题。 使用某些摄取端点的客户可能遭遇延迟处理或摄取新日志数据失败. 没有利用受影响摄取途径的服务仍在运作。 我们将在一小时内提供最新情况.
- investigating
我们正在继续调查这一问题.
- identified
这一问题已经确定,一个解决办法正在实施之中.
- identified
我们正在继续努力解决这个问题。
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
53 Loggly incidents · 2020年12月 — official updates, affected components, duration and resolution details.
我们目前正在调查一个影响部分客户的日志摄入的问题。 使用某些摄取端点的客户可能遭遇延迟处理或摄取新日志数据失败. 没有利用受影响摄取途径的服务仍在运作。 我们将在一小时内提供最新情况.
我们正在继续调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
我们正在继续努力解决这个问题。
这一事件已经得到解决.
自动翻译自官方事件更新。
客户影响 少数客户的数据摄入和警报延迟,没有实时处理。 没有丢失客户数据。 事件更新 2026年9月3日,协调世界时10:52,一个基础设施组件无法使用,导致处理积压并延迟了警戒处理. 一个单独的警报分组问题延迟了向待命小组的通知,从而延长了作出反应的时间。 此外,由于我们的应用信息问题,我们无法在应用中及时提供客户通知。 18小时49分后事件得到完全解决. 数据处理和警报处理已恢复正常,没有丢失客户数据。 我们正在审查我们的警戒分组行为、服务回收程序和客户通知机制,以减少今后类似事件的可能性和影响.
自动翻译自官方事件更新。
On July 12, 2026, we experienced delays in our alerting system, resulting in an interruption to alert processing for some Loggly customers. The issue was traced to a production scheduler service responsible for evaluating and scheduling alerts. Due to resource exhaustion on the host, the scheduler was unable to operate normally, preventing alert jobs from being process downstream. The team restored service by increasing the capacity of the affected host, returning resource utilization to healthy levels and allowing the scheduler to resume normal operation. Following the remediation, alert processing has since been operating normally.
At 5:46 AM PDT we started experiencing delays in our alerting system caused by a network provider issue. The issue is resolved and we are monitoring the recovery.
This incident has been resolved.
We are investigating an issue with our alerting system that started at 13:06 UTC.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing issue with our Front-End application. Our engineers are investigating.
We have identified an issue with an outside provider
We are continuing to work on a fix for this issue.
We have identified an issue with an outside provider and are monitoring the situation.
We are continuing to monitor the issue
This incident has been resolved.
Our engineers have identified an issue with log ingestion starting at 07:22 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Our engineers have identified an issue with log ingestion starting at 20:56 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Our engineers have identified an issue with log ingestion starting at 06:02 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
At 1:56 PM PDT we were alerted that search was unavailable. We identified the problem and applied a fix and search is once again available.
Our engineers have identified an issue with log ingestion starting at 20:22 PDT . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
We are continuing to investigate the issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Our engineers have identified an issue with log ingestion starting at 14:08 PDT. All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We experienced an issue with our volume data reporting service and are working on restoring it.
The issue has been identified and a fix is being implemented.
A fix is still being implemented and the next update will be 06:00 UTC
A fix has been implemented and we are monitoring the results.
We are continuing to monitor.
This incident has been resolved.
We are experiencing issue with our Front-End application. Our engineers are investigating.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our engineers have identified an issue with log ingestion starting at 5:28 AM PDT . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our engineers have identified an issue with log ingestion starting at 11:54AM PDT . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Issue started: 14:05 UTC Issue resolved: 14:54am UTC Issue with sending mail for account invites and password reset. Other mail notifications should have still worked.
Our engineers have identified an issue with log ingestion starting at 5:52 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our engineers have identified an issue with log ingestion starting at 2:25 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.