Is Loggly down?

Customer Impact A small number of customers experienced delayed data ingestion and alerts that were not processed in real time. No customer data was lost. Incident Update On September 3, 2026, at 10:52 PM UTC, an infrastructure component became unavailable, resulting in a processing backlog and delays in alert handling. A separate alert-grouping issue delayed notification to the on-call team, extending the time to response. In addition, an issue with our in-app messaging prevented us from providing timely customer notifications within the app. The incident was fully resolved after 18 hours and 49 minutes. Data processing and alert handling have returned to normal, and no customer data was lost. We are reviewing our alert-grouping behavior, service-recovery procedures, and customer notification mechanisms to reduce the likelihood and impact of similar incidents in the future.

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.