We are still working on the usa4-adj problem and are fully aware of the issue. We hope to have it back online soon

Again, please don’t open support tickets regarding this problem – we are aware of it. Opening more tickets will not get your service back online any quicker!

Due to the server becoming unresponsive, it has been rebooted and should be back online within a few minutes. You may need to restart your AutoDJ if it doesn’t come back up automatically, but for 99% of people it will be automatic.

We are aware some clients are still having connectivity issues. To rectify any remaining issues we are working on adding a connection to Cogent who is On-Net within our datacenter. They are currently not part of  our bandwidth providers.

Abovenet has updated us they are trying to reroute the cut fiber using an alternate path because they are unable to gain access to the fiber for repair due to fire.

We do not have any ETA/ETR estimates at this time. As soon as we have more information we will send another update.

The network issue is a bend in one of our fibers to NYC, provided by Abovenet. Techs have identified where the problem is, have prepped for the work in the manhole they need to be in.

The fiber cut is being workedon by Abovenet. They are saying that the c rew is in place to replace the span of fiber that is damaged.

They are not able to give us an estimated time of repair yet.

There seems to be an issue affecting some routes to the USA premium network, affecting the following servers:

usa1-pn, usa2-pn, usa1-adj, usa2-adj, usa3-adj and usa4-adj

I have a ticket open with the datacentre and will update this post as I get info.

UPDATE: This seems to have been resolved and seems to have been a temporary issue with a supplier outside of the network.

This only seems to be affecting usa1-pn and usa2-pn but I’ve listed this post under other servers that could be affected at all.

There seems to be packet loss on the network, I have an emergency ticket open with the datacentre and hope to get this resolved asap – in fact as I’m writing this things seem to be improving already.

UPDATE (19:35): I can confirm that as I was finishing the post, buffering completely stopped. I’ve also had word from the network admin confirming that they were working on blocking a flood which lasted for about 5-10 minutes.