Samanage Outage History

Samanage is up right now

Samanage had 44 outages in the last 2 years totaling 308h 54m of downtime — averaging 1.8 incidents per month.

There were 44 Samanage outages since May 28, 2024 totaling 308h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.samanage.com

Major May 6, 2026

Error 500: Service interruption

Detected by Pingoru
May 06, 2026, 01:23 PM UTC
Resolved
May 06, 2026, 03:25 PM UTC
Duration
2h 1m
Affected: Application (North America)
Timeline · 3 updates
  1. investigating May 06, 2026, 01:23 PM UTC

    We are aware of an issue that caused the application to be unavailable for a few minutes. Our team is currently investigating the cause and monitoring the service to ensure it remains stable. Further updates will be posted here as more information becomes available.

  2. monitoring May 06, 2026, 01:53 PM UTC

    The services are currently operating normally, and our engineering team is closely monitoring system performance to ensure continued stability. We will provide additional updates here if we observe any further impact or if additional action is required.

  3. resolved May 06, 2026, 03:25 PM UTC

    Following an extended monitoring period, the issue has not reappeared, and no further impact has been reported. Services are operating normally, and we consider this incident resolved. If you experience any additional issues or need assistance, please contact us at [email protected], and our team will be glad to help.

Read the full incident report →

Minor April 3, 2026

Slow Performance & Error 500

Detected by Pingoru
Apr 03, 2026, 12:33 PM UTC
Resolved
Apr 03, 2026, 09:57 PM UTC
Duration
9h 23m
Affected: Application (North America)
Timeline · 7 updates
  1. investigating Apr 03, 2026, 12:33 PM UTC

    We are currently investigating reports of slow performance and intermittent Error 500 issues in SolarWinds Service Desk. Our team is working to resolve this as quickly as possible.

  2. identified Apr 03, 2026, 01:00 PM UTC

    We've identified the cause of the reported issue and are working on a fix as quickly as possible. Thank you for your patience.

  3. monitoring Apr 03, 2026, 01:42 PM UTC

    We have completed the fix for this issue and will continue to monitor the situation to ensure stability.

  4. investigating Apr 03, 2026, 03:08 PM UTC

    We have observed unexpected behavior following the recent fix and are currently reviewing the issue. Our team is continuing to investigate while working to ensure full stability. We appreciate your patience and will provide further updates as soon as more information becomes available.

  5. investigating Apr 03, 2026, 04:29 PM UTC

    We are actively investigating continued unexpected behavior following a recent fix. Our team is working to ensure full stability. We appreciate your patience and will share another update as soon as more information is available.

  6. monitoring Apr 03, 2026, 05:56 PM UTC

    We are seeing improved results on our end and are continuing to monitor performance closely. We are also working to confirm whether customers are seeing similar improvement while we continue to ensure full stability. We appreciate your patience and will provide another update as soon as more information becomes available.

  7. resolved Apr 03, 2026, 09:57 PM UTC

    We have continued to monitor the service and have not observed any further issues. Additionally, we have not received any new reports of slow performance or Error 500 errors. At this time, the incident is considered resolved. If further assistance is needed, please contact [email protected]. Thank you for your patience throughout this process.

Read the full incident report →

Minor March 18, 2026

Overlapping Text Fields in Incident/Service Request Tickets

Detected by Pingoru
Mar 18, 2026, 09:46 AM UTC
Resolved
Mar 18, 2026, 01:30 PM UTC
Duration
3h 43m
Affected: Application (North America)Application (EMEA)
Timeline · 7 updates
  1. investigating Mar 18, 2026, 09:14 AM UTC

    We have received reports of overlapping text fields in Incident/Service Request tickets and are currently investigating the issue.

  2. identified Mar 18, 2026, 09:46 AM UTC

    We have identified the cause of the overlapping text fields and are currently working on a fix. We will provide updates as soon as progress is made. Thank you for your patience and understanding.

  3. identified Mar 18, 2026, 11:52 AM UTC

    We are still working on fixing the issue. We will continue to monitor the situation and provide updates as they become available.

  4. identified Mar 18, 2026, 11:57 AM UTC

    We will deploy a fix shortly. We will provide an update once it has been deployed.

  5. identified Mar 18, 2026, 12:26 PM UTC

    We are in the process of deploying the fix. We will keep you updated as progress continues.

  6. monitoring Mar 18, 2026, 12:47 PM UTC

    We have completed the deployment of the fix for this issue and will continue to monitor the situation to ensure stability.

  7. resolved Mar 18, 2026, 01:30 PM UTC

    This issue has been resolved.

Read the full incident report →

Minor February 2, 2026

Application Slow Performance

Detected by Pingoru
Feb 02, 2026, 03:49 PM UTC
Resolved
Feb 02, 2026, 06:55 PM UTC
Duration
3h 5m
Affected: Application (North America)
Timeline · 6 updates
  1. investigating Feb 02, 2026, 03:49 PM UTC

    We are currently experiencing performance issues in the Service Desk Application, and our team is investigating. This impacts actions such as navigating through the Incidents page and other areas of the app.

  2. investigating Feb 02, 2026, 04:21 PM UTC

    We have identified elevated load on the database layer in our US Service Desk environment. This is leading to slow page loads, delayed data population, and intermittent 504 Gateway Timeout errors for some customers. Our team is actively working on remediation to reduce database load and restore normal performance. During this time, the application may run more slowly than normal. We will provide the next update within 30 minutes or sooner as we make progress.

  3. identified Feb 02, 2026, 04:50 PM UTC

    We are still actively working on reducing the elevated database load in our US Service Desk environment. The underlying issue has been identified, and our team is continuing remediation efforts to stabilize performance.

  4. identified Feb 02, 2026, 05:26 PM UTC

    We are continuing to work on a fix for this issue and further reducing the elevated database load in our US Service Desk environment. Some users may still experience intermittent slowness or timeouts while we complete these changes. We will provide another update within 30 minutes or as soon as we have more information.

  5. monitoring Feb 02, 2026, 06:19 PM UTC

    We have implemented a fix for the database load issue affecting our US Service Desk environment; we are restarting a set of frontend services to complete remediation. Users should now begin to see improved performance and fewer timeouts as these changes take effect. Our team will continue to closely monitor the environment and will provide another update once performance is fully stabilized.

  6. resolved Feb 02, 2026, 06:55 PM UTC

    We have resolved the database load issue affecting our US Service Desk environment and restarted the impacted frontend services. Since then, performance has remained stable under monitoring, and we are no longer observing elevated errors or timeouts. This incident is now closed. If you continue to experience slowness or errors, please contact SolarWinds Support or open a ticket so we can investigate further.

Read the full incident report →

Minor January 27, 2026

US & AU Data Centers - Service Request Approval Workflow Issue

Detected by Pingoru
Jan 27, 2026, 06:51 PM UTC
Resolved
Jan 28, 2026, 04:49 AM UTC
Duration
9h 58m
Affected: Application (North America)Application (APAC)
Timeline · 7 updates
  1. investigating Jan 27, 2026, 06:51 PM UTC

    We are currently investigating an issue affecting Service Requests for customers in the US and AU regions. Initial findings indicate that when the approval process is configured to use the Incident Assignee as the approver, the workflow may terminate unexpectedly with the following error: “The task [Task Name] has been automatically declined per predefined approval conditions because the approval step contains unknown approvers.” Our engineering teams are actively working to identify the root cause and determine a resolution. If you have questions, are experiencing related issues, or would like to provide additional details, please contact us via chat or email at [email protected]. We will continue to provide updates as more information becomes available.

  2. investigating Jan 27, 2026, 07:48 PM UTC

    Our team is actively investigating the issue, which may be related to a recent deployment. We are working to identify the root cause and resolve it, and we will provide updates as more information becomes available. Thank you for your patience.

  3. investigating Jan 27, 2026, 09:49 PM UTC

    Our team is continuing to investigate the issue and is focused on identifying the root cause and resolving it as quickly as possible. We will provide updates as new details become available. Thank you for your patience.

  4. identified Jan 27, 2026, 11:13 PM UTC

    We have identified the root cause of the issue affecting Service Request approval workflows for customers in the US and AU regions. We are currently testing a fix. Once testing is complete, we will proceed with deployment and share further updates.

  5. identified Jan 28, 2026, 03:44 AM UTC

    The fix we had in place did not resolve the issue as expected. Our Engineering team has identified and is currently working on a resolution. Our team is preparing for the deployment, which is expected to be completed within the next hour. If this changes, we will provide an update immediately.

  6. identified Jan 28, 2026, 03:44 AM UTC

    The fix we had in place did not resolve the issue as expected. Our Engineering team has identified and is currently working on a resolution. Our team is preparing for the deployment, which is expected to be completed within the next hour. If this changes, we will provide an update immediately.

  7. resolved Jan 28, 2026, 04:49 AM UTC

    This issue has been resolved.

Read the full incident report →

Minor January 27, 2026

AU DC - New Tickets Not Appearing in Service Desk UI

Detected by Pingoru
Jan 27, 2026, 12:03 AM UTC
Resolved
Jan 27, 2026, 02:09 AM UTC
Duration
2h 6m
Affected: Application (APAC)
Timeline · 3 updates
  1. investigating Jan 27, 2026, 12:03 AM UTC

    We are currently investigating an issue affecting the Service Desk in the AU Data Center, where newly created objects, such as tickets and assets, are not appearing in the user interface as expected. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

  2. monitoring Jan 27, 2026, 01:23 AM UTC

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

  3. resolved Jan 27, 2026, 02:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 12, 2026

New tickets that were created are not appearing in the Service Desk UI

Detected by Pingoru
Jan 12, 2026, 07:43 AM UTC
Resolved
Jan 12, 2026, 12:28 PM UTC
Duration
4h 45m
Affected: Application (APAC)
Timeline · 2 updates
  1. investigating Jan 12, 2026, 07:43 AM UTC

    We are currently investigating an issue affecting the Service Desk in the AU Data Center. New tickets are not appearing in the UI. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

  2. resolved Jan 12, 2026, 12:28 PM UTC

    This issue has been resolved.

Read the full incident report →

Minor January 9, 2026

Scheduled Service Catalog Item Not Running

Detected by Pingoru
Jan 09, 2026, 09:27 AM UTC
Resolved
Jan 09, 2026, 11:00 AM UTC
Duration
1h 32m
Affected: Application (EMEA)
Timeline · 4 updates
  1. investigating Jan 09, 2026, 09:27 AM UTC

    We are aware of an issue affecting a scheduled Service Desk service catalog item in our EU data center. Our team is actively working to identify the root cause and restore normal functionality. Additional updates will be shared as they become available.

  2. identified Jan 09, 2026, 09:36 AM UTC

    Additional resources have been allocated to help manage the queue. As a result, the backlog is now being processed efficiently, and pending items are getting cleared. Additional updates will be shared as they become available.

  3. monitoring Jan 09, 2026, 10:09 AM UTC

    Scheduled service catalog item are now being processed. We are monitoring the situation closely to ensure continued stability.

  4. resolved Jan 09, 2026, 11:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 6, 2026

Service Desk Application Performance Degradation

Detected by Pingoru
Jan 06, 2026, 10:47 AM UTC
Resolved
Jan 06, 2026, 05:59 PM UTC
Duration
7h 11m
Affected: Application (EMEA)
Timeline · 4 updates
  1. investigating Jan 06, 2026, 10:47 AM UTC

    We are currently investigating an issue affecting Service Desk in EU Data Center. Round-robin assignment and Automation Rules process are delayed, this affects automation assigning and or updating incidents. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

  2. investigating Jan 06, 2026, 11:14 AM UTC

    We have identified performance degradation in the Service Desk application within EUDC. This issue is impacting multiple functionalities of the application. Our team is actively investigating the issue and working to identify the root cause. Further updates will be shared as more information becomes available.

  3. monitoring Jan 06, 2026, 02:32 PM UTC

    Service Desk EU data-center degradation issue affecting the application has now been restored. System performance is now normal and the application is operating as expected. We continue to monitor performance closely to ensure ongoing stability and reliability.

  4. resolved Jan 06, 2026, 05:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 5, 2026

Service Desk Round-Robin Assignment Option Problem

Detected by Pingoru
Jan 05, 2026, 01:35 PM UTC
Resolved
Jan 05, 2026, 07:13 PM UTC
Duration
5h 38m
Affected: Application (EMEA)
Timeline · 3 updates
  1. investigating Jan 05, 2026, 01:35 PM UTC

    We are currently investigating an issue affecting the Service Desk in our EU Data Center. The round-robin automatic assignment is not working as expected, and newly created tickets are not being assigned to a user or group automatically. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

  2. monitoring Jan 05, 2026, 04:13 PM UTC

    A fix has been implemented. We will continue to monitor until we can confirm that no additional impact is expected.

  3. resolved Jan 05, 2026, 07:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Possible Service Desk Features Degradation

Detected by Pingoru
Nov 18, 2025, 01:32 PM UTC
Resolved
Nov 18, 2025, 11:17 PM UTC
Duration
9h 45m
Affected: Application (North America)Application (EMEA)Application (APAC)
Timeline · 5 updates
  1. monitoring Nov 18, 2025, 01:32 PM UTC

    We're currently experiencing an upstream vendor outage. This is affecting services, and you may see failures in items such as VA (Virtual Agent) functionality and custom domain routing. Our teams are monitoring the situation closely for updates.

  2. monitoring Nov 18, 2025, 02:16 PM UTC

    Our upstream vendor are continue working on restoring service for application services.

  3. monitoring Nov 18, 2025, 03:33 PM UTC

    Based on the recent update from our upstream vendor they have implemented a fix to resolve the issue. Our team is continuously monitoring for updates.

  4. monitoring Nov 18, 2025, 07:23 PM UTC

    Our upstream vendor’s issue has been resolved, and we are no longer seeing any impact on our platform. We will continue to closely monitor the fix.

  5. resolved Nov 18, 2025, 11:17 PM UTC

    This issue has been resolved. Please contact us at [email protected] if you need further assistance.

Read the full incident report →

Minor October 20, 2025

Performance Issue with Service Desk US Datacenter

Detected by Pingoru
Oct 20, 2025, 11:29 AM UTC
Resolved
Oct 21, 2025, 02:33 AM UTC
Duration
15h 3m
Affected: Application (North America)
Timeline · 8 updates
  1. identified Oct 20, 2025, 11:29 AM UTC

    We experienced a temporary service disruption with our cloud service provider in the N. Virginia region, causing increased error rates and latency. Mitigation efforts by the cloud service provider are underway, and most services are showing signs of recovery though some services still lay affected. Some delays may persist as our cloud service provider is working through backlogs—Thank you for your patience.

  2. identified Oct 20, 2025, 11:33 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Oct 20, 2025, 12:49 PM UTC

    There has been some improvement with our service provider mitigating the issue, we will continue to monitor the situation.

  4. monitoring Oct 20, 2025, 12:57 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Oct 20, 2025, 05:04 PM UTC

    We are continuing to monitor for any further issues and will provide updates as necessary.

  6. monitoring Oct 20, 2025, 08:39 PM UTC

    We’ve observed some improvement from our service provider in mitigating the issue. We are continuing to monitor for any further issues and will provide updates as necessary.

  7. monitoring Oct 20, 2025, 11:22 PM UTC

    Following the resolution of the issue with AWS, we are keeping the service desk environment into Monitoring mode to ensure full operational stability. At this time, we are closely monitoring the environment to confirm everything is functioning as expected. If you are still experiencing any issues, please don’t hesitate to reach out to us at [email protected].

  8. resolved Oct 21, 2025, 02:33 AM UTC

    This issue has been resolved. Please contact us at [email protected] if you need further assistance.

Read the full incident report →

Minor October 2, 2025

US Data Center - System Performance Issues

Detected by Pingoru
Oct 02, 2025, 08:15 PM UTC
Resolved
Oct 02, 2025, 11:24 PM UTC
Duration
3h 9m
Affected: Application (North America)
Timeline · 3 updates
  1. investigating Oct 02, 2025, 08:15 PM UTC

    We are aware of the reports regarding system slowness and performance issues. We are investigating the issue to identify the cause and implement a resolution as quickly as possible.

  2. monitoring Oct 02, 2025, 08:45 PM UTC

    A fix has been implemented. We will continue to monitor the system closely to ensure there is no further impact.

  3. resolved Oct 02, 2025, 11:24 PM UTC

    After monitoring the Service Desk application for the past few hours, we can confirm that it has remained stable following the recent fix implementation. We are now marking this issue as resolved. If you experience any further issues, please don’t hesitate to contact us at [email protected].

Read the full incident report →

Notice September 30, 2025

Error 500 - Computer Assets Details Page

Detected by Pingoru
Sep 30, 2025, 09:58 AM UTC
Resolved
Sep 30, 2025, 02:13 PM UTC
Duration
4h 14m
Affected: Inventory (EMEA)Inventory
Timeline · 4 updates
  1. investigating Sep 30, 2025, 09:58 AM UTC

    We are receiving reports regarding computer details page that is throwing an Error 500. Our team is aware of this matter and currently doing further investigation. This is affecting both US and EU data-centers, we apologize for the inconvenience at this time. Further updates will be shared once root cause of the problem is identified.

  2. identified Sep 30, 2025, 10:59 AM UTC

    We have identified the problem and our engineering team is now working for the fix deployment. Further update will be shared once deployment is tested completed.

  3. monitoring Sep 30, 2025, 12:36 PM UTC

    Our engineering team has implemented a fix to address the reported issue regarding Error 500. We are currently monitoring the stability of the application to ensure the problem has been resolved. If you continue to experience any issues, please contact us at [email protected] for further assistance.

  4. resolved Sep 30, 2025, 02:13 PM UTC

    This issue has been resolved. Please contact us at [email protected] if you need further assistance.

Read the full incident report →

Notice September 4, 2025

User Search Not Returning Results

Detected by Pingoru
Sep 04, 2025, 02:49 PM UTC
Resolved
Sep 05, 2025, 08:24 AM UTC
Duration
17h 35m
Affected: Application (North America)
Timeline · 4 updates
  1. identified Sep 04, 2025, 02:49 PM UTC

    There is a known issue when searching user via Global Search or user search field within users list for Service Desk instance residing in US Data Center. Even though the user exist in Service Desk the query is not returning results, we are aware of this problem and our engineering team is currently working to fix it as soon as possible. We apologize for the inconvenience and your patience.

  2. identified Sep 04, 2025, 04:59 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Sep 04, 2025, 06:56 PM UTC

    We've identified the issue affecting user search functionality, including global search and context search. A fix has been prioritized, but it must be applied outside of production hours due to its nature. We appreciate your patience and will provide an update once the fix is implemented.

  4. resolved Sep 05, 2025, 08:24 AM UTC

    Our engineering team has recently implemented a fix to address the reported issue regarding user search. We are currently monitoring the stability of the application to ensure the problem has been resolved. If you continue to experience any issues, please contact us at [email protected] for further assistance.

Read the full incident report →

Minor September 3, 2025

US Data Center – Intermittent Latency

Detected by Pingoru
Sep 03, 2025, 05:15 PM UTC
Resolved
Sep 04, 2025, 12:32 AM UTC
Duration
7h 17m
Affected: Application (North America)
Timeline · 5 updates
  1. investigating Sep 03, 2025, 05:15 PM UTC

    We are currently investigating reports of intermittent latency when navigating through the Service Desk UI in the US Data Center. We understand the impact this may have on your operations. Further updates will be provided as soon as more information becomes available.

  2. investigating Sep 03, 2025, 06:53 PM UTC

    We are actively investigating the reported performance issues affecting navigation within the Service Desk UI. Further updates will be provided as soon as more information becomes available.

  3. investigating Sep 03, 2025, 08:37 PM UTC

    Our engineering team continues to thoroughly investigate the reported issue. We are committed to identifying the root cause and implementing a resolution as swiftly as possible. Please reach out to [email protected] if you require urgent assistance.

  4. monitoring Sep 03, 2025, 09:37 PM UTC

    Our engineering team has recently implemented a potential fix to address the reported issue. We are currently monitoring the stability of the application to ensure the problem has been resolved. If you continue to experience any issues, please contact us at [email protected] for further assistance.

  5. resolved Sep 04, 2025, 12:32 AM UTC

    We are marking this issue as resolved, as the Service Desk application has remained stable for the past several hours. Should the issue resurface or if you require further assistance, please don't hesitate to contact us at [email protected].

Read the full incident report →

Minor August 26, 2025

Delay in Incident Creation

Detected by Pingoru
Aug 26, 2025, 01:59 PM UTC
Resolved
Aug 26, 2025, 05:07 PM UTC
Duration
3h 7m
Affected: Application (North America)
Timeline · 3 updates
  1. investigating Aug 26, 2025, 01:59 PM UTC

    We are investigating an issue that impacts incidents created by email.

  2. investigating Aug 26, 2025, 04:41 PM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 26, 2025, 05:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 29, 2025

Groups and Queue name not showing at the Assigned To field

Detected by Pingoru
Jul 29, 2025, 12:24 PM UTC
Resolved
Jul 29, 2025, 04:35 PM UTC
Duration
4h 11m
Timeline · 4 updates
  1. identified Jul 29, 2025, 12:24 PM UTC

    We are seeing minor problem using the Assigned To field where Group name and Queues are not showing up when assigning Incidents. This is affecting all customers in all Data centers. The change was due to a recent deployment that would enable Group Assignment feature for all "New Accounts" regrettably it enabled for all the accounts in production. A Quick fix is to go to Setup - Global Settings - Service Desk Settings and disabled the "Assigned to field displays only users and queue members" option. Our engineering team is working on a fix to be deployed in production that will revert the account back to the previous selected option (on or off).

  2. monitoring Jul 29, 2025, 03:30 PM UTC

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

  3. monitoring Jul 29, 2025, 03:31 PM UTC

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

  4. resolved Jul 29, 2025, 04:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 25, 2025

Latency in the SWSD app

Detected by Pingoru
Jul 25, 2025, 02:10 PM UTC
Resolved
Jul 25, 2025, 05:30 PM UTC
Duration
3h 20m
Affected: Application (North America)
Timeline · 4 updates
  1. investigating Jul 25, 2025, 02:10 PM UTC

    We are currently investigating a potential widespread issue with the Service Desk tool, including Slow loading times, Automation rules not running as expected, email creation delays, and round-robin assignments not working as expected.

  2. identified Jul 25, 2025, 02:41 PM UTC

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

  3. monitoring Jul 25, 2025, 03:58 PM UTC

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

  4. resolved Jul 25, 2025, 05:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 17, 2025

US Data Center - Issues with the Incident module

Detected by Pingoru
Jul 17, 2025, 06:21 PM UTC
Resolved
Jul 17, 2025, 09:09 PM UTC
Duration
2h 48m
Affected: Application (North America)
Timeline · 3 updates
  1. investigating Jul 17, 2025, 06:21 PM UTC

    We are currently experiencing an issue affecting the Service Desk. While new tickets are being created successfully, users may notice the following symptoms: - Newly created tickets appear to be stuck in a "loading" state when accessed through the UI. - The incident index page does not reflect newly created tickets. - New comments may not show in the comments section. - Inability to access and update new incidents. We are actively investigating the root cause. We will provide updates as more information becomes available and work toward restoring full functionality as quickly as possible. Please contact [email protected] if you have any questions.

  2. monitoring Jul 17, 2025, 07:14 PM UTC

    We observed a spike in database read operations, which resulted in temporary delays in the system's performance. The issue has since been mitigated, and all services are operating normally. A full root cause analysis (RCA) will be shared once available. We appreciate your patience and understanding.

  3. resolved Jul 17, 2025, 09:09 PM UTC

    This issue has been resolved. Please contact us at [email protected] if you need further assistance.

Read the full incident report →

Minor June 12, 2025

Issues with Process Integrations

Detected by Pingoru
Jun 12, 2025, 06:31 PM UTC
Resolved
Jun 13, 2025, 12:34 AM UTC
Duration
6h 3m
Affected: Application (North America)Application (EMEA)Application (APAC)
Timeline · 5 updates
  1. investigating Jun 12, 2025, 06:31 PM UTC

    We are currently experiencing an issue where Process Integrations are not functioning as expected. Our team is actively investigating to determine the root cause. We will provide updates as soon as more information becomes available.

  2. identified Jun 12, 2025, 06:50 PM UTC

    We've identified the root cause of the issue affecting Process Integrations and are actively working on a fix. Our team is prioritizing this and aiming to resolve it as quickly as possible.

  3. identified Jun 12, 2025, 08:47 PM UTC

    A key deployment dependency was affected by a broad internet outage, which caused a delay in delivering the fix. The dependency is now back online, and our team is working to deploy the fix shortly. We appreciate your patience and will provide another update as soon as the deployment is complete.

  4. monitoring Jun 12, 2025, 09:43 PM UTC

    The issue has been addressed and a fix has been deployed. We are actively monitoring the system to ensure everything is functioning as expected and that no further issues arise.

  5. resolved Jun 13, 2025, 12:34 AM UTC

    The issues affecting Process Integrations have been resolved. If you continue to experience any problems or need further assistance, please contact us at [email protected].

Read the full incident report →

Minor June 2, 2025

Problems with the Service Desk Virtual Agent

Detected by Pingoru
Jun 02, 2025, 06:52 PM UTC
Resolved
Jun 03, 2025, 01:46 AM UTC
Duration
6h 54m
Affected: Application (North America)Application (EMEA)Application (APAC)
Timeline · 5 updates
  1. investigating Jun 02, 2025, 06:52 PM UTC

    We would like to inform you that the SolarWinds Service Desk Virtual Agent is currently experiencing issues impacting the service portal and its integrations with Microsoft Teams and Slack. A support ticket has been opened with our vendor, and their support team has acknowledged the issue. We are actively working with them to resolve the problem. We will share further updates as soon as more information becomes available.

  2. investigating Jun 02, 2025, 08:58 PM UTC

    Our team continues to investigate this issue. We do not yet have a confirmed timeline for resolution, but we are focused on resolving the problem as quickly as possible. We will share further updates as soon as more information becomes available.

  3. monitoring Jun 02, 2025, 11:10 PM UTC

    Updates on the current status of the SolarWinds environments across various regions: EU and AU Production Environments: These are now up and running, and the Virtual Agent's functionalities are working as expected. US Region: We are still awaiting an update on the US production environment. We will share more information as soon as it becomes available.

  4. monitoring Jun 02, 2025, 11:57 PM UTC

    We’re pleased to inform you that the fix has been successfully deployed to the US Data Center, and the Virtual Agent is now fully operational across all regions. Our teams will continue to monitor the environment closely to ensure ongoing stability and confirm that no further impact is expected.

  5. resolved Jun 03, 2025, 01:46 AM UTC

    The issues affecting the SolarWinds Service Desk Virtual Agent have been fully resolved. If you continue to experience any problems or need further assistance, please don’t hesitate to contact us at [email protected].

Read the full incident report →

Major May 26, 2025

APAC DC – Emails Not Generating New Incidents

Detected by Pingoru
May 26, 2025, 10:54 PM UTC
Resolved
May 27, 2025, 09:19 AM UTC
Duration
10h 25m
Affected: Email Services (APAC)
Timeline · 3 updates
  1. investigating May 26, 2025, 03:20 PM UTC

    We are currently investigating an issue affecting the Service Desk in the APAC Data Center. At this time, emails sent to the Service Desk are not generating new incidents or adding comments to existing ones. Our team is actively working to identify the root cause and will provide updates as soon as more information is available. We appreciate your patience and understanding.

  2. identified May 26, 2025, 10:54 PM UTC

    We’ve identified the root cause of the issue and are actively working on implementing a fix. Our team is collaborating closely with our email vendor to resolve this high-priority issue as quickly as possible. We’ll continue to keep you informed and will notify you as soon as the fix has been successfully deployed. Thank you for your continued patience and understanding.

  3. resolved May 27, 2025, 09:19 AM UTC

    Creating incident via email in AU Site is now resolved. Please contact us at [email protected] if you need further assistance.

Read the full incident report →