Scalyr Outage History

Pingoru has recorded 50 incidents for Scalyr: 5 in the last 12 months and 0 in the last 90 days.

50incidents recorded

5last 12 months

0last 90 days

8 hourstypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking Scalyr in April 2026, so earlier months are not shown. Hover a bar for its value.

Show as a table

Incidents, newest first

Started Jul 06, 2026, 06:00 AM UTC· resolved Jul 06, 2026, 03:50 PM UTC

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.

Started Jun 10, 2026, 04:51 PM UTC· resolved Jun 11, 2026, 04:37 PM UTC

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.

Started May 08, 2026, 10:31 PM UTC· resolved May 09, 2026, 01:30 AM UTC

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.

Started Apr 23, 2026, 07:45 PM UTC· resolved Apr 23, 2026, 07:47 PM UTC

monitoring Apr 23, 2026, 07:45 PM UTC

Apologies for the correction. To clarify the scope of the incident mentioned in our previous post, the following environments were impacted: app.eu.scalyr.com, app.us1.dataset.com, and app.eu1.dataset.com.
resolved Apr 23, 2026, 07:47 PM UTC

This incident has been resolved.

Started Apr 23, 2026, 04:00 PM UTC· resolved Apr 23, 2026, 07:16 PM UTC

resolved Apr 23, 2026, 07:34 PM UTC

Between 4:05 PM and 7:16 PM UTC, some DataSet customers may have experienced intermittent issues logging into the UI via SSO. This incident was limited strictly to the login interface; data ingestion and query capabilities were not impacted and remained fully operational throughout the event. Our engineering team has successfully mitigated the issue via a system rollback, and all SSO login services have been fully restored.

Started Sep 09, 2025, 05:03 PM UTC· resolved Sep 09, 2025, 08:29 PM UTC

investigating Sep 09, 2025, 05:03 PM UTC

We are currently investigating an issue affecting both search and ingestion functionality on app.scalyr.com.
identified Sep 09, 2025, 06:02 PM UTC

The issue has been identified and our Engineering teams are working to implement a fix. We will continue to provide updates on our progress.
resolved Sep 09, 2025, 08:29 PM UTC

All services have been fully restored and the incident is now resolved. We have validated that all systems are functioning normally. Thank you for your patience throughout this incident.

Started Jan 16, 2025, 06:39 PM UTC· resolved Jan 17, 2025, 12:22 AM UTC

investigating Jan 16, 2025, 06:39 PM UTC

We are currently investigating this issue.
investigating Jan 16, 2025, 07:10 PM UTC

We are in the process of rolling back the change and restarting the affected servers. Some accounts may observe a gradual recovery of their logs.
identified Jan 16, 2025, 07:48 PM UTC

A misconfiguration deployment caused server resource allocation issues. A rollback and server restart have been initiated to address the problem.
monitoring Jan 16, 2025, 10:01 PM UTC

Recovery is currently in progress. The estimated time for full ingestion restoration is approximately 60 to 90 minutes from now.
resolved Jan 17, 2025, 12:22 AM UTC

The backlog data caused by the incident has been fully recovered in all regions

Started Oct 24, 2024, 04:54 PM UTC· resolved Oct 24, 2024, 11:49 PM UTC

investigating Oct 24, 2024, 04:54 PM UTC

We are currently investigating the issue.
identified Oct 24, 2024, 05:13 PM UTC

A misconfiguration deployed this morning prevented the servers from scaling up correctly. We are currently in the process of manually scaling up the servers to manage the ingestion volume effectively.
identified Oct 24, 2024, 06:11 PM UTC

The aggressive scaling out of servers led to a 500 error when loading the page due to hitting the database connection limit. We are currently in the process of scaling the servers back in, and the error should be resolved shortly.
monitoring Oct 24, 2024, 07:11 PM UTC

The UI should now be loading as expected. We have increased the database connection limit to accommodate more concurrent connections. The queue is in the process of recovering and is gradually processing the backlog of events.
resolved Oct 24, 2024, 11:49 PM UTC

This incident has been resolved.