Updates:

• Time: Nov. 6, 2015, 9:44 p.m.
  Status: Resolved
  Update: Dear Customer, the *umCloud is available again and all services are recovered. The Cloud GUI is unlocked. You will receive a detailed incident report within the next days. We apologize again for any inconvenience.
• Time: Nov. 6, 2015, 9:11 p.m.
  Status: Monitoring
  Update: Dear Customer, all systems are still stable. Currently we continue to reactivate some remaining virtual machines and the corresponding services. For security reasons the cloud access is still locked for our customers.
• Time: Nov. 6, 2015, 8:10 p.m.
  Status: Identified
  Update: Dear Customer, all systems are still stable. Currently we are activating the remaining deactivated virtual machines. For security reasons the cloud access is still locked, but the virtual machines are reachable.
• Time: Nov. 6, 2015, 7:18 p.m.
  Status: Identified
  Update: Dear *um-Customer, We have identified the potential cause and currently eliminating the cause. Since 90 minutes all systems are up and running stable. Only a small part of the virtual machines are currently not available. For security reasons the cloud GUI is currently locked. We apologize again for any inconvenience this disruption may have caused you
• Time: Nov. 6, 2015, 6 p.m.
  Status: Identified
  Update: Dear *umCustomer, We were able to mitigate the possible cause and we are still working on a full restoration of our services. New Updates, we will send directly to you.
• Time: Nov. 6, 2015, 4:40 p.m.
  Status: Identified
  Update: Dear *umCustomer, We focused our analysis on the possible root cause. We are also in direct communication with the manufacturers. However, we can not exclude that new isolated vServer must restarted for now. Of cause we will inform you of the further progress.
• Time: Nov. 6, 2015, 3:21 p.m.
  Status: Identified
  Update: Dear *umCustomer, We regret to inform you that the elimination of the service limitation has not been completed. A possible cause is identified. We continue to work with high prio on the restoration of the service. Further updates will be communicated to you hourly.
• Time: Nov. 6, 2015, 2:27 p.m.
  Status: Identified
  Update: Dear *umCustomer, Restoring the affected vServer is still in the status "on going“. All departments analyzing in parallel the service restriction. We keep you informed with all new informations as soon as possible.
• Time: Nov. 6, 2015, 1:39 p.m.
  Status: Identified
  Update: Dear *um Customer, We continue to work on a full recovery of our services. To achieve this it may become necessary to perform a targeted reset of some vServer. Furthermore we point out that only the "Availability Zone BER1" is concerned. We apologize for any inconvenience this disruption may have caused you. Thank you for your understanding. Sincerely, Your *um Support-Team
• Time: Nov. 6, 2015, 12:51 p.m.
  Status: Identified
  Update: Dear *um Customer, After more extensive analysis, we could not detect any new service limitations in our environment. We continue to work on a complete restoration of the affected vServer.
• Time: Nov. 6, 2015, 12:20 p.m.
  Status: Identified
  Update: Dear *um Customer, We have analyzed the environment in order to avoid further restrictions. We now start with the restart of the affected vServer.
• Time: Nov. 6, 2015, 11:32 a.m.
  Status: Identified
  Update: Dear *um Customer, We are working as quickly as we can to restore services. Currently, at least one of your vServers has been affected and will be restarted shortly, after which services will be restored to normal.
• Time: Nov. 6, 2015, 11:12 a.m.
  Status: Identified
  Update: We're currently experiencing a degradation of our *umCloud service. We're busy investigating and analyzing the incident and working on recovering all services.