Loggly Outage History
8 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Loggly Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | Indexing DelayThis incident has been resolved. | 4h 38m | Resolved |
| Oct 28, 2026 | Indexing DelayThis incident has been resolved. | 4h 35m | Resolved |
| Oct 6, 2026 | Degraded Data CollectionThis incident has been resolved. | 3h 47m | Resolved |
| Sep 4, 2026 | Delayed data ingestionCustomer 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… | -1305 min | Resolved |
| Aug 7, 2026 | Alerting DelayOn 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… | 0 min | Resolved |
| May 11, 2026 | Alerts IssueThis incident has been resolved. | 1h 14m | Resolved |
| Jan 21, 2026 | Alerts IssueThis incident has been resolved. | 43 min | Resolved |
| Nov 18, 2025 | Front-end experiencing issuesThis incident has been resolved. | 4h 12m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Loggly incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Loggly Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Loggly acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Loggly outage in this window ran 4h 38m, against a mean recovery of 2h 44m. If you depend on Loggly in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.