Istoricul incidentelor Scalyr

1. 6 iulie 2026 la 20:24 UTCresolved

   Calendarul evenimentelor 6 iul. 06:58 UTC: Suntem conştienţi de întârzierile ingestiei datelor care afectează unii clienţi. Puteţi prezenta o întârziere a apariţiei unor date noi. 6 iul. 10:23 UTC: Problema de bază a fost identificată și echipele noastre de inginerie lucrează în mod activ pentru a implementa un fix. Vă vom oferi actualizări în timp ce progresăm și vă vom aprecia răbdarea în timp ce rezolvăm incidentul. 6 iul. 15:50 UTC: Serviciile au fost restaurate, iar noi lucrăm pentru a valida sănătatea sistemelor voastre. În timp ce ingerarea datelor a fost reluată, există încă un backlog temporar al datelor prelucrate. Pe măsură ce sistemele ajung din urmă, puteţi vedea o creştere a alertelor întârziate. Acesta este un comportament așteptat.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iunie 2026 la 16:51 UTCidentified

   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.

2. 11 iunie 2026 la 16:37 UTCresolved

   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.

1. 8 mai 2026 la 22:31 UTCinvestigating

   We are currently investigating this issue.

2. 8 mai 2026 la 22:50 UTCidentified

   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.

3. 9 mai 2026 la 00:07 UTCmonitoring

   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.

4. 9 mai 2026 la 01:30 UTCresolved

   This incident has been resolved.

1. 23 aprilie 2026 la 19:45 UTCmonitoring

   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.

2. 23 aprilie 2026 la 19:47 UTCresolved

   This incident has been resolved.

1. 23 aprilie 2026 la 19:34 UTCresolved

   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.

1. 9 septembrie 2025 la 17:03 UTCinvestigating

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

2. 9 septembrie 2025 la 18:02 UTCidentified

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

3. 9 septembrie 2025 la 20:29 UTCresolved

   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.

1. 22 ianuarie 2025 la 00:00 UTCidentified

   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

2. 22 ianuarie 2025 la 02:14 UTCresolved

   This incident has been resolved.

1. 16 ianuarie 2025 la 18:39 UTCinvestigating

   We are currently investigating this issue.

2. 16 ianuarie 2025 la 19:10 UTCinvestigating

   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.

3. 16 ianuarie 2025 la 19:48 UTCidentified

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

4. 16 ianuarie 2025 la 22:01 UTCmonitoring

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

5. 17 ianuarie 2025 la 00:22 UTCresolved

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

1. 24 octombrie 2024 la 16:54 UTCinvestigating

   We are currently investigating the issue.

2. 24 octombrie 2024 la 17:13 UTCidentified

   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.

3. 24 octombrie 2024 la 18:11 UTCidentified

   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.

4. 24 octombrie 2024 la 19:11 UTCmonitoring

   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.

5. 24 octombrie 2024 la 23:49 UTCresolved

   This incident has been resolved.

1. 26 septembrie 2024 la 19:36 UTCidentified

   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.

2. 26 septembrie 2024 la 23:38 UTCresolved

   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.

1. 20 septembrie 2024 la 19:21 UTCinvestigating

   We are currently investigating this issue.

2. 20 septembrie 2024 la 19:34 UTCidentified

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

3. 20 septembrie 2024 la 20:33 UTCresolved

   This incident has been resolved.

1. 12 septembrie 2024 la 18:29 UTCresolved

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

1. 10 septembrie 2024 la 17:41 UTCidentified

   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

2. 10 septembrie 2024 la 18:12 UTCmonitoring

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

3. 10 septembrie 2024 la 18:23 UTCresolved

   This incident has been resolved.

1. 19 august 2024 la 02:05 UTCinvestigating

   We are currently investigating this issue.

2. 19 august 2024 la 02:45 UTCidentified

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

3. 19 august 2024 la 03:48 UTCresolved

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

1. 12 iulie 2024 la 18:57 UTCinvestigating

   The issue is currently under investigation

2. 12 iulie 2024 la 19:15 UTCmonitoring

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

3. 12 iulie 2024 la 19:39 UTCresolved

   This incident has been resolved.

1. 2 mai 2024 la 16:59 UTCinvestigating

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

2. 2 mai 2024 la 18:52 UTCmonitoring

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

3. 2 mai 2024 la 23:28 UTCresolved

   Queue server ingestion delay has been resolved.

1. 1 mai 2024 la 22:08 UTCresolved

   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

1. 11 aprilie 2024 la 08:18 UTCinvestigating

   The issue is currently under investigation

2. 11 aprilie 2024 la 08:25 UTCidentified

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

3. 11 aprilie 2024 la 08:55 UTCidentified

   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

4. 11 aprilie 2024 la 09:39 UTCmonitoring

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

5. 11 aprilie 2024 la 10:00 UTCresolved

   This incident has been resolved

1. 10 aprilie 2024 la 21:48 UTCidentified

   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.

2. 10 aprilie 2024 la 22:42 UTCidentified

   A fix has been implemented and validation in progress.

3. 10 aprilie 2024 la 23:30 UTCmonitoring

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

4. 11 aprilie 2024 la 00:03 UTCresolved

   This incident has been resolved.

1. 8 martie 2024 la 18:27 UTCresolved

   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.