All systems are operational

Past Incidents

6th April 2020

Ceph health Snapshot problems on weekend

We had some problems with our storage, which caused that no snapshots were created on the past weekend. So there are NO backups since Friday 00:30 AM.

We fixed all issues and the snapshots will be created normally tonight.

20th March 2020

Snapshot problems tonight

We had some problems tonight with our storage, which caused that no snapshots were created. So there are NO backups for tonight.

We fixed all issues and the snapshots will be created normally tonight.

3rd March 2020

Let's Encrypt CAA Rechecking Bug

The Let's Encrypt community recently discovered a bug in the Let's Encrypt certificate authority code, described here: https://community.letsencrypt.org/t/2020-02-29-caa-rechecking-bug/114591

Unfortunately, this means they need to revoke the certificates that were affected by this bug, which may includes one or more of your certificates.

If you're not able to renew your certificate by March 4, the date they are required to revoke these certificates, visitors to your site will see security warnings until you do renew the certificate. Your ACME client documentation should explain how to renew.

If you are using Certbot, the command to renew is: certbot renew --force-renewal

If you are a NWS-App customer or a managed services customer with active MyEngineer contract, we will take care about renewing your certificates.

In case you want to test your certificates by yourself, just use this command (with your domain)

curl -XPOST -d 'fqdn=example.org' https://unboundtest.com/caaproblem/checkhost Please check the the output, it should be look like this: "The certificate currently available on example.org is OK. It is not one of the certificates affected by the Let's Encrypt CAA rechecking problem. Its serial number is 03a1c95bdaa36a8268327f2253cbd3ba243"

If you need help, please do not hesitate to contact us.

  • We renew all affected Certificates

  • 29th February 2020

    Hypervisors net-openstack-hv10 hardware failure

    We expiering some trouble with one of our openstack-hypervisors since 4:00 AM , so some virtual machines with local SSD-Storage was not able to access the their images as fast as usual. We are investigating for a possible migration of the virtual machines to another hypervisor and fixing the hardware.

  • Due to a hardware-failure we had some trouble with net-openstack-hv10. Virtual Machines was not able to access their base-images.

    For maintenance we moved ceph-based virtual machines to other hypervisors. We also replaced non-working parts of the server in the datacenter.

    Server is now up and now fully operational

  • 7th February 2020

    Hypervisors net-openstack-hv8 restricted access to local SSDs

    We had some trouble with one of our openstack-hypervisors between 10:10 AM and 10:50 AM, so some virtual machines with local SSD-Storage was not able to access the their images. We found the root cause for the outage.