Is Loggly down?

Last checked just now
Current status
Loggly is up

No incidents right now.

Loggly is operational right now. Last checked just now; the most recent incident resolved 2d ago.

Real-time Loggly status, recent outages, and incident history: pulled directly from Loggly's official status page at status.loggly.com every 5 minutes. Pingoru tracks 9 Loggly services and has captured 5 incidents in the last 90 days (99.26% uptime). Get email, Slack, Discord, or webhook alerts the moment Loggly reports a new incident, free for 3 monitors, no credit card.

Users who monitor Loggly also follow these Analytics services: New Relic Grafana Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch FullStory View all 8,000+ providers
Loggly uptime 99.26% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 4h 38m
    Started Oct 29, 2026, 08:09 AM UTC · Resolved Oct 29, 2026, 12:48 PM UTC
    Indexing DataSearch AvailabilityAlerts
    Timeline · 3 updates
    • investigating · Oct 29, 2026, 08:09 AM UTC

      Our monitoring has detected an issue causing delayed data indexing for a small subset of customers. Some users may experience delays before new data appears in search and dashboards. We are actively working on a resolution and will provide updates as they become available.

    • monitoring · Oct 29, 2026, 09:15 AM UTC

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

    • resolved · Oct 29, 2026, 12:48 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 4h 35m
    Started Oct 28, 2026, 08:35 PM UTC · Resolved Oct 29, 2026, 01:11 AM UTC
    Indexing DataSearch AvailabilityAlerts
    Timeline · 6 updates
    • investigating · Oct 28, 2026, 08:35 PM UTC

      Our engineers have identified an issue with log ingestion starting at 12:50:32 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.

    • investigating · Oct 28, 2026, 09:38 PM UTC

      We're continuing to investigate the issue. More updates will come in one hour.

    • investigating · Oct 28, 2026, 10:38 PM UTC

      We're continuing to investigate the issue. More updates will be published in two hours.

    • identified · Oct 29, 2026, 12:35 AM UTC

      The issue has been identified, the fix has been tested and about to be implemented.

    • monitoring · Oct 29, 2026, 12:56 AM UTC

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

    • resolved · Oct 29, 2026, 01:11 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 3h 47m
    Started Oct 06, 2026, 12:16 PM UTC · Resolved Oct 06, 2026, 04:04 PM UTC
    Data Collection & Storage
    Timeline · 7 updates
    • 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.

    • investigating · Oct 06, 2026, 12:17 PM UTC

      We are continuing to investigate this issue.

    • investigating · Oct 06, 2026, 01:19 PM UTC

      We are continuing to investigate this issue.

    • identified · Oct 06, 2026, 01:42 PM UTC

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

    • identified · Oct 06, 2026, 02:42 PM UTC

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

    • identified · Oct 06, 2026, 03:42 PM UTC

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

    • resolved · Oct 06, 2026, 04:04 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved –
    Started Sep 03, 2026, 10:52 PM UTC · Resolved Sep 03, 2026, 10:52 PM UTC
    Timeline · 1 update
    • 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.

    Latest: 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 Septem…

  5. Resolved –
    Started Aug 07, 2026, 08:54 PM UTC · Resolved Aug 07, 2026, 08:54 PM UTC
    Timeline · 1 update
    • 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.

    Latest: 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 sch…

Incident record

Since April 2026 · Statuspage by Atlassian · 9 components checked every 5 minutes
55incidents recorded
8last 12 months
5last 90 days
2 hourstypical duration, 12 months

The longest incident in the last year, Indexing Delay on October 29, 2026, ran for 5 hours.

Most affected components, last 12 months

  • Alerts4
  • Indexing Data2
  • Search Availability2
  • Data Collection & Storage1
  • Website Availability1

Latest incidents

  • Indexing Delay October 29, 2026 · 5 hours · degraded service

    Our monitoring has detected an issue causing delayed data indexing for a small subset of customers. Some users may experience delays before new data appears in…

  • Indexing Delay October 28, 2026 · 5 hours · degraded service

    Our engineers have identified an issue with log ingestion starting at 12:50:32 PDT. All customer data continues to be collected and stored, but indexing of all…

  • Degraded Data Collection October 6, 2026 · 4 hours · notice

    We are currently investigating an issue affecting log ingestion for a subset of customers. Customers using certain ingestion endpoints may experience delayed…

Outage history

Past 90 days · 5 incidents View full outage history →
  • Started Oct 29, 2026, 08:09 AM UTC · Resolved Oct 29, 2026, 12:48 PM UTC · 4h 38m
  • Started Oct 28, 2026, 08:35 PM UTC · Resolved Oct 29, 2026, 01:11 AM UTC · 4h 35m
  • Started Oct 06, 2026, 12:16 PM UTC · Resolved Oct 06, 2026, 04:04 PM UTC · 3h 47m
  • Started Sep 03, 2026, 10:52 PM UTC · Resolved Sep 03, 2026, 10:52 PM UTC · –
  • Started Aug 07, 2026, 08:54 PM UTC · Resolved Aug 07, 2026, 08:54 PM UTC · –