3stepIT incident

Intermittent downtime problems within Skype and Asset Management - monitoring continues

Notice Resolved View vendor source →

3stepIT experienced a notice incident on August 21, 2018 affecting 3StepIT AssetNG Service and 3StepIT 3ConnectIT Service and 1 more component, lasting 6d 2h. The incident has been resolved; the full update timeline is below.

Started
Aug 21, 2018, 09:57 AM UTC
Resolved
Aug 27, 2018, 12:22 PM UTC
Duration
6d 2h
Detected by Pingoru
Aug 21, 2018, 09:57 AM UTC

Affected components

3StepIT AssetNG Service3StepIT 3ConnectIT Service3StepIT Webshop Service3stepIT Website Service

Update timeline

  1. monitoring Aug 21, 2018, 09:57 AM UTC

    We have now re-opened the latest incident, and will investigate further.

  2. monitoring Aug 21, 2018, 10:46 AM UTC

    Skype for business is identified as a partial problem at the moment

  3. monitoring Aug 21, 2018, 11:17 AM UTC

    We have currently put Skype for business for an immediate maintenance break to sort out the problem

  4. monitoring Aug 21, 2018, 11:31 AM UTC

    We are currently limiting the Skype service to keep the problem under control. Configuration work continues to fix the root cause. Apologies for the inconvenience.

  5. monitoring Aug 21, 2018, 12:12 PM UTC

    Asset Management is currently back to normal operational mode. We keep monitoring the status, and continue working with the fix for Skype.

  6. monitoring Aug 22, 2018, 07:58 AM UTC

    An update to Skype will be performed during this evening. Meanwhile extensive monitoring of the existing configuration still takes place.

  7. monitoring Aug 23, 2018, 08:29 AM UTC

    We are still working with the subject and monitoring the latest configuration changes. Short intermittent outages with Skype and AssetNG may still occur, as we fine tune the new configuration. Apologies for the inconvenience.

  8. monitoring Aug 23, 2018, 11:59 AM UTC

    We are continuing to monitor for any further issues. For the moment it seems that the problem has been sorted out now.

  9. resolved Aug 27, 2018, 12:22 PM UTC

    The issue is now resolved. The required configuration changes have now been made and monitored. Apologies for the inconvenience.