Devolutions Outage History

Devolutions is up right now

Devolutions had 28 outages in the last 2 years totaling 6h 27m of downtime — averaging 1.2 incidents per month.

There were 28 Devolutions outages since December 3, 2024 totaling 6h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.devolutions.net

Minor March 3, 2025

Connectivity issues with Devolutions Hub

Detected by Pingoru
Mar 03, 2025, 05:25 PM UTC
Resolved
Mar 03, 2025, 08:16 PM UTC
Duration
2h 50m
Affected: FranceUSCanadaAustralia
Timeline · 6 updates
  1. investigating Mar 03, 2025, 05:25 PM UTC

    Intermittent timeouts are affecting service.

  2. investigating Mar 03, 2025, 05:50 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 03, 2025, 05:59 PM UTC

    We are continuing to investigate this issue.

  4. identified Mar 03, 2025, 06:44 PM UTC

    An issue with our provider has been identified, causing intermittent connectivity problems for some users. We will continue to monitor the situation and post updates as they become available.

  5. monitoring Mar 03, 2025, 07:08 PM UTC

    Our provider has implemented a fix, and we are seeing a significant reduction in timeouts across our servers. We continue to monitor the situation closely to ensure full stability. Further updates will be provided as necessary.

  6. resolved Mar 03, 2025, 08:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 4, 2024

Partial outage on Devolutions Hub Canada

Detected by Pingoru
Dec 04, 2024, 09:20 PM UTC
Resolved
Dec 05, 2024, 12:46 AM UTC
Duration
3h 25m
Affected: Canada
Timeline · 6 updates
  1. investigating Dec 04, 2024, 09:20 PM UTC

    We are currently investigating an issue related to Identity Provider group synchronisation.

  2. identified Dec 04, 2024, 10:49 PM UTC

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

  3. identified Dec 05, 2024, 12:20 AM UTC

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

  4. monitoring Dec 05, 2024, 12:39 AM UTC

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

  5. monitoring Dec 05, 2024, 12:43 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Dec 05, 2024, 12:46 AM UTC

    This incident has been resolved.

Read the full incident report →