Loggly Outage History

Loggly is up right now

Loggly had 3 outages in the last 2 years totaling 5h 26m of downtime — averaging 0.1 incidents per month.

There were 3 Loggly outages since November 18, 2025 totaling 5h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.loggly.com

Notice August 7, 2026

Alerting Delay

Detected by Pingoru
Aug 07, 2026, 08:54 PM UTC
Resolved
Aug 07, 2026, 08:54 PM UTC
Duration
Timeline · 1 update
  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

Detected by Pingoru
May 11, 2026, 09:06 PM UTC
Resolved
May 11, 2026, 10:21 PM UTC
Duration
1h 14m
Affected: Alerts
Timeline · 2 updates
  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

Detected by Pingoru
Nov 18, 2025, 12:07 PM UTC
Resolved
Nov 18, 2025, 04:19 PM UTC
Duration
4h 12m
Affected: Website Availability
Timeline · 7 updates
  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 →