Loggly Outage History

Loggly is up right now

Pingoru has recorded 53 incidents for Loggly: 6 in the last 12 months and 3 in the last 90 days.

Source: status.loggly.com

53incidents recorded
6last 12 months
3last 90 days
100 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Loggly in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202611 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202610 of 744 (0%)
September 202610 of 720 (0%)
October 202614 of 511 (1%)

Incidents, newest first

Notice October 6, 2026 Degraded Data Collection 3h 47m Data Collection & Storage

Started Oct 06, 2026, 12:16 PM UTC· resolved Oct 06, 2026, 04:04 PM UTC

  1. investigating Oct 06, 2026, 12:16 PM UTC

    We are currently investigating an issue affecting log ingestion for a subset of customers. Customers using certain ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. We will provide an update within the hour.

  2. investigating Oct 06, 2026, 12:17 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 06, 2026, 01:19 PM UTC

    We are continuing to investigate this issue.

  4. identified Oct 06, 2026, 01:42 PM UTC

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

  5. identified Oct 06, 2026, 02:42 PM UTC

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

  6. identified Oct 06, 2026, 03:42 PM UTC

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

  7. resolved Oct 06, 2026, 04:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 3, 2026 Delayed data ingestion –

Started Sep 03, 2026, 10:52 PM UTC· resolved Sep 03, 2026, 10:52 PM UTC

  1. resolved Sep 04, 2026, 08:37 PM UTC

    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.

Read the full incident report →

Notice August 7, 2026 Alerting Delay –

Started Aug 07, 2026, 08:54 PM UTC· resolved Aug 07, 2026, 08:54 PM UTC

  1. resolved Aug 07, 2026, 08:54 PM UTC

    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.

Read the full incident report →

Notice May 11, 2026 Alerts Issue 1h 14m Alerts

Started May 11, 2026, 09:06 PM UTC· resolved May 11, 2026, 10:21 PM UTC

  1. monitoring May 11, 2026, 09:06 PM UTC

    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.

  2. resolved May 11, 2026, 10:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2025 Front-end experiencing issues 4h 12m Website Availability

Started Nov 18, 2025, 12:07 PM UTC· resolved Nov 18, 2025, 04:19 PM UTC

  1. investigating Nov 18, 2025, 12:07 PM UTC

    We are experiencing issue with our Front-End application. Our engineers are investigating.

  2. identified Nov 18, 2025, 12:19 PM UTC

    We have identified an issue with an outside provider

  3. identified Nov 18, 2025, 12:20 PM UTC

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

  4. identified Nov 18, 2025, 12:22 PM UTC

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

  5. monitoring Nov 18, 2025, 12:28 PM UTC

    We have identified an issue with an outside provider and are monitoring the situation.

  6. monitoring Nov 18, 2025, 02:25 PM UTC

    We are continuing to monitor the issue

  7. resolved Nov 18, 2025, 04:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 4, 2025 Indexing Delay 1h 55m Indexing Data

Started Feb 04, 2025, 06:03 PM UTC· resolved Feb 04, 2025, 07:59 PM UTC

  1. investigating Feb 04, 2025, 06:03 PM UTC

    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.

  2. identified Feb 04, 2025, 06:05 PM UTC

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

  3. monitoring Feb 04, 2025, 07:01 PM UTC

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

  4. monitoring Feb 04, 2025, 07:29 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 04, 2025, 07:59 PM UTC

    This incident has been resolved.

Read the full incident report →