Scalyr outage history

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.

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.

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.

We are currently investigating this issue.

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.

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.

This incident has been resolved.

Apologies for the corrections. 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.

This incident has been resolved.

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.

We are currently investigating an issue affecting both search and ingestion functionality on app.scalyr.com.

The issue has been identified and our Engineering teams are working to implement a fix. We will continue to provide updates on our progress.

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.

Ingestions were temporarily interrupted at approximately 8:30 PM GMT due to an authorization issue on the cluster. Recovery is currently underway, and users can expect the events to be backfilled slowly to their accounts

This incident has been resolved.

We are currently investigating this issue.

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.

A misconfiguration deployment caused server resource allocation issues. A rollback and server restart have been initiated to address the problem.

Recovery is currently in progress. The estimated time for full ingestion restoration is approximately 60 to 90 minutes from now.

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

We are currently investigating the issue.

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.

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.

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.

This incident has been resolved.

Ingestion on app.us1.dataset.com returns 429 and 500 status codes since 2 pm GMT. A significant increase in ingestion has overloaded the cluster. The issue has been identified and we're working on a fix.

The ingestion pipeline and supporting systems are fully functional. While there is no suspected data loss it may take up to 24 hours to work through the backlog of data that has built up during the incident to be fully processed.

We are currently investigating this issue.

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

This incident has been resolved.

Ingest for users on app.eu.scalyr.com was effectively halted at 3pm GMT. The issue was fully mitigated at 5:45pm GMT.

The correct build of the query servers failed to initialize, leading to performance issues with query execution. The root cause has been identified and the problem has been mitigated for users on app.scalyr.com. The recovery is still in progress for users on app.dataset.com

All query servers were restarted and query performance is back to normal

This incident has been resolved.

We are currently investigating this issue.

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

Ingestion traffic is now back to normal. The issue has been mitigated

The issue is currently under investigation

Queries are now functional on app.eu.scalyr.com after restarting the machines with the OOM issue.

This incident has been resolved.

We are investigating an ingestion issue on app.us1.dataset.com that began around 1450 GMT

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

Queue server ingestion delay has been resolved.

Failure to update the certification causes ingestion issues on the EU cluster. It has been reverted and the ingestion has resumed since 21:25 GMT

The issue is currently under investigation

The issue has been identified. A new endpoint in the last deployment broke the web application. A revert is in progress

The issue was affecting some users on app.scalyr.com and app.eu.scalyr.com. The service on those two endpoints have been restored. We are still in the process of restoring services on app.dataset.com and app.eu.dataset.com

All sites are now restored and the services are now back online

This incident has been resolved

Some users of app.scalyr.com, app.us1.dataset.com, and app.eu1.dataset.com are receiving intermittent 429 errors on search and dashboards. We have identified the issue and are working to remediate it.

A fix has been implemented and validation in progress.

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

This incident has been resolved.

Users of app.us1.dataset.com experienced slow queries and errors between 16:50 UTC and 17:50 UTC. We have applied a fix to address the immediate issue and are implementing a code change as a long-term solution.