Problems with resolving .hypernode.io

Our DNS infrastructure has been running stable for the past 12 hours. We'll continue to monitor and improve the infrastructure.

As the attack seems to calm down, operations are returning on our nodes and internal infrastructure. We continue working on increasing our stability to mitigate future incidents.

Sadly as we're trying to resolve this as quick we can, an alternative temporary solution is to use the direct IP if you're using an external DNS service, you can get this with using dig with our alternative DNS server, make sure to point your A-record to the resulting IP-address:
```
dig @80.84.227.137 abc.hypernode.io A
```

We hope this won't be needed for long and we can return operations as soon as possible.

We have identified our DNS server is being flooded with packets. We are activating our counter-measures and continue monitoring the situation.

We're currently seeing extremely degraded performance across our platform, this seems to be related to our DNS resolving to hypernode.io , we are actively investigating and will update when possible.