Is Scalyr down?

Last checked 10m ago
Current status
Scalyr is up

No incidents right now.

Official status page: https://status.scalyr.com · Polled every 5 minutes · 1 component tracked

Scalyr is operational right now. Last checked 10m ago; the most recent incident resolved 26d ago.

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

Users who monitor Scalyr also follow these DevOps services: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 6,000+ providers
Scalyr uptime 100.00% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jul 06, 2026, 08:24 PM UTC · Resolved Jul 06, 2026, 06:00 AM UTC
    Timeline · 1 update
    • resolved · Jul 06, 2026, 08:24 PM UTC

      Events timeline Jul 6, 06:58 UTC: We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data. Jul 6, 10:23 UTC: The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident. Jul 6, 15:50 UTC: Services have been restored, and we are working to validate the health of your systems. While data ingestion has resumed, there is a temporary backlog of data still being processed. As systems catch up, you may see a surge in delayed alerts. This is expected behavior.

    Latest: Events timeline Jul 6, 06:58 UTC: We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data. Jul 6, 10:23 UTC: The…

  2. Resolved 23h 45m
    Started Jun 10, 2026, 04:51 PM UTC · Resolved Jun 11, 2026, 04:37 PM UTC
    Timeline · 2 updates
    • identified · Jun 10, 2026, 04:51 PM UTC

      Starting June 9 at 20:55 UTC, ingestion delays affected accounts on app.us1.dataset.com and app.eu1.dataset.com. The issue was identified, and a hotfix was deployed on June 10 at approximately 08:00 UTC. Ingestion has returned to normal in the EU environment. We are currently processing the remaining backlog in the US environment to restore normal performance.

    • resolved · Jun 11, 2026, 04:37 PM UTC

      As of June 11 at 8:11 UTC, the backlog events for accounts on app.us1.dataset.com have been completely processed, and the incident has been resolved.

    Latest: As of June 11 at 8:11 UTC, the backlog events for accounts on app.us1.dataset.com have been completely processed, and the incident has been resolved.

  3. Resolved 2h 58m
    Started May 08, 2026, 10:31 PM UTC · Resolved May 09, 2026, 01:30 AM UTC
    Timeline · 4 updates
    • investigating · May 08, 2026, 10:31 PM UTC

      We are currently investigating this issue.

    • identified · May 08, 2026, 10:50 PM UTC

      We have identified an issue with a backend cluster that is currently disrupting event ingestion. Our engineering team is performing a system failover to restore normal operations.

    • monitoring · May 09, 2026, 12:07 AM UTC

      Rebalancing our ingestion servers has stabilized the incoming data volume. Engineering is adding capacity to accelerate the processing of the data backlog. The impacted cluster has resumed ingestion at normal levels. All affected data has been queued since the beginning of the incident, so there is no data loss.

    • resolved · May 09, 2026, 01:30 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 3 incidents View full outage history →