Telephone — Today at 12:33 AM
Update: We're currently waiting on ticket response from OVH. We've filed it and also called in to their support, but still have no ETA. Our current belief is that they will not respond for several more hours. We're looking at figuring out some alternate solutions, but expect that we will be down for at least another 6-12 hours. We apologize and we'll update you as soon as we know anything. To be 100% clear: Your characters and data are safe. Homecoming is in no danger and we will resume service ASAP.(edited)
Telephone — Today at 8:53 AM
Update: OVH assigned our ticket a little while ago. They've asked us to perform some testing which we are about to do.
Telephone — Today at 10:31 AM
Update: We've completed the testing OVH asked for and sent them all our results. We're now waiting on them to work on or escalate the issue.
Telephone — Today at 12:13 PM
Update: We're still waiting on a reply from OVH. In the meantime, we've got an alternate overlay networking technology we're working on setting up as a backup to vRack until the issue is fixed. We've just completed our first connection with it and are now in the process of rolling it out to our cluster.
Telephone — Today at 2:28 PM
Update: We're still waiting on a reply from OVH. In the meantime, we've also lost the ability to access one of our servers, so we've filed a second ticket for that server. We still have no ETA for when we will be up. We tried an alternate method of overlay networking in hopes that it would allow us to resume service, but unfortunately the first attempt was unsuccessful. We'll continue attempts to get this to work.
UPDATE ACCORDING TO DISCORD!