Samanage Outage History

Samanage is up right now

There were 3 Samanage outages since March 18, 2026 totaling 17h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.samanage.com

Major April 29, 2026

Error 500: Service interruption

Detected by Pingoru
Apr 29, 2026, 07:01 PM UTC
Resolved
Apr 29, 2026, 11:28 PM UTC
Duration
4h 27m
Affected: Application (North America)API
Timeline · 4 updates
  1. investigating Apr 29, 2026, 07:01 PM UTC

    We are aware of an issue that caused the application to be unavailable for approximately two 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. investigating Apr 29, 2026, 07:08 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 29, 2026, 07:56 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.

  4. resolved Apr 29, 2026, 11:28 PM UTC

    After an extended period of monitoring, the issue has not resurfaced and we have not received any additional reports of impact. Service is operating normally and we are considering this incident resolved. If you continue to experience any issues or need further assistance, please contact us via email at [email protected], and our team will be happy 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 →

Looking to track Samanage downtime and outages?

Pingoru polls Samanage's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Samanage reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Samanage alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Samanage for free

5 free monitors · No credit card required