Störungsverlauf von Solarwinds

We are currently experiencing service degradation due to an issue with our cloud provider. Our teams are working closely with their engineers to resolve the impact as quickly as possible. We’ll provide an update as soon as more information becomes available.

We are currently experiencing service degradation due to an issue with our cloud provider. Our teams are working closely with their engineers to resolve the impact as quickly as possible. We’ll provide an update as soon as more information becomes available.

This incident has been resolved.

Between 07:10 AM and 11:54 AM UTC on October 20, 2025, we experienced a delay in alert notifications triggered by metric thresholds. The issue was caused by a service degradation at our cloud provider, which impacted the timely processing and delivery of alerts. The provider has since resolved the underlying issue, and our alerting systems have fully recovered.

Ingest pipeline congestion resulted in a backlog. We have disabled processing for some elements and things are stabilizing. Disabled elements will be re-enabled in a controlled fashion once all other customers are caught up

We are continuing to investigate this issue.

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

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

This incident has been resolved.

There have been reports of login issues, which we are actively investigating.

An issue has been addressed and the situation seems to be improving rapidly. We expect the processing backlog to be entirely cleared shortly, at which time it is anticipated that API response times should improve.

This incident has been resolved.

Connections to one of the shard servers are experiencing issues, which impacts environments hosted on that shard. We are investigating the issue.

We are continuing to investigate this issue.

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

Most backlog has cleared and we are monitoring the progress

All backlogs have cleared, and no issues are evident with the service at this time.

There is an issue with event processing that may cause alerts to be delayed or not issued. Investigation continues.

A fix has been implemented and we are monitoring the results. There is a processing backlog, which we expect will clear shortly.

This incident has been resolved. All backlog has been cleared.

There is an issue with event processing that may cause alerts to be delayed or not issued. Investigation continues.

We have detected some slowdowns in Query Sample processing, and are currently investigating the issue

Last night, our team identified the issue and applied a fix. Conditions have improved and we are currently monitoring for the query sample processing backlog to clear

We are continuing to monitor for any further issues.

While conditions have improved, the backlog has not yet cleared. We continue to monitor for the query sample processing backlog to clear.

The Query Sample Processing backlog has continued to improve but is not yet 100% finished. Many customer environments are current, with a few seeing about a 1-day lag.

The majority of samples are now being processed in real-time, and we continue to monitor the remaining backlog

A small number of environments are still affected, and we are expecting to clear the remaining backlog by tomorrow (Wednesday 6th)

This incident has been resolved.

The issue has been identified. Possible fixes are under investigation.

The issue has been identified and a fix is being implemented. Currently, a few customer environments may see data gaps in some charts.

Over the last few days, we have continued to see a large amount data coming into our ingestion pipeline. We have tried to address this issue by increasing our infrastructure capacity and have tuned the configurations to the maximum allowed limits. In parallel, we have paused one of the problematic environments temporarily to not inundate the ingestion pipeline. These actions are helping to process the data at an improved speed. However, it may still take 2-3 days to get through all the backlog. Until such time, some customers may see some data gaps in monitoring.

Although progress has been made in reducing the backlog in the ingestion pipeline for certain environments, the processing speed is not meeting our desired pace. We are actively examining the source and quantity of incoming data to find ways to decrease the amount of data being ingested, aiming to enhance processing efficiency. This involves tasks such as relocating high-volume workloads for manual load balancing. Additionally, the architecture team is ongoing in their assessment of scaling options to further address the issue.

Our recent initiative to relocate demanding workloads has significantly boosted the performance of our ingestion pipeline. Processing has become more efficient, and we anticipate that within the next 24 hours, the system is expected to clear the entire backlog, based on the current rate and trend. We're actively monitoring the situation and concurrently working on further optimizing processing of incoming data.

The delayed ingestion issue was resolved approximately at 11:00 pm EST on 11/22/2023. All customer environments are functioning normally. We are continuing to monitor the environment. If you are experiencing any difficulties, please contact us at https://support.solarwinds.com/

We are currently investigating the issue.

We are in the process of reverting to a stable version. Will update the status once the reversion happens.

We have reverted to a previous version in a controlled environment to monitor further.

We have reverted our changes and the issue is resolved

We are currently investigating this issue.

Issue identified & addressed, everything catching up, continuing to monitor.

This incident has been resolved.

Querysample processing is functional, but may be delayed/degraded at this time; we are working on the issue.

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

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

This incident has been resolved.

We have identified issues in Event processing which may affect some clients; we are working to remedy the issue

A fix has been implemented and we are monitoring the results. We believe that there is zero impact at this time.

This incident has been resolved.

Situation seems to have stabilized; we have backfilled gaps and continue to monitor. There may be further incidents until the infrastructure is completely stable.

This incident has been resolved.

We are currently investigating this issue.

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

This incident has been resolved.

We are currently investigating this issue.

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

This incident has been resolved.

We are currently investigating a system wide outage.

The application is back up. We are monitoring the state of the system.

All systems have recovered. We will continue to monitor.

Metrics processing has fallen behind, and some clients are not able to view their hosts.

We are processing the metrics backlog, and are continuing to monitor the system.

This incident has been resolved.

We are currently investigating an issue with the "Dashboards" page not loading any data.

The dashboards are now operational.

This incident has been resolved.

We are currently experiencing an issue with users not being able to see any data on the "Alerts" page. We are investigating the issue.

The "Alerts" page has been fixed. Users can view the data on the UI now.