Post-issue writeup - We believe that the issue originated from a neighbor user (someone that has a server on the same host machine as us) that was misusing their server with a very high CPU/Network load. This caused performance issues (the CPU was so badly hit that system-critical tasks went on a 60+ second timeout) and caused the network to be completely absent. We're unsure what this user has done to cause all of this, but we've informed the provider and they told us that they will take measures to prevent similar incidents from happening again.

The services appear to be fully operational now. Thanks for your patience.

The hosting provider fixed the problem on their end. We're currently monitoring to confirm everything is back online