Before saying a server is 'dead', it would be better to perform a traceroute to the server, so you can see if the problem is at your ISP's side, or at our side.
You can do this by going to your Windows' start menu, clicking on "Run...", then type in "cmd", and press enter.
A black window will pop up. Type in "tracert <server>" (replace <server> with the Voxalot server you are registered with).
If the connection between your PC and the Voxalot server is just fine, then something like this would show up:
Code:
1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 10 ms 5350C801.cable.casema.nl [83.80.200.1]
3 11 ms 9 ms 7 ms 10.0.33.2
4 12 ms 12 ms 13 ms 5350043A.cable.casema.nl [83.80.4.58]
5 10 ms 12 ms 14 ms 20ge-chnl.amsix.tc2.leaseweb.net [195.69.144.215]
6 15 ms 12 ms 8 ms 10ge-1-0-0.r1.sbp.leaseweb.net [83.149.127.30]
7 10 ms 10 ms 12 ms proxy01.eu1.voxalot.com [85.17.19.194]
If the connection between your PC and the Voxalot server is unavailable due to a faulty router/switch at your ISP then something like this would show up:
Code:
1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 10 ms 5350C801.cable.casema.nl [83.80.200.1]
3 11 ms 9 ms 7 ms 10.0.33.2
4 12 ms 12 ms 13 ms 5350043A.cable.casema.nl [83.80.4.58]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
If the connection between your PC and the Voxalot server is unavailable due to a faulty router/switch at Voxalot's ISP, then something like this would show up:
Code:
1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 10 ms 5350C801.cable.casema.nl [83.80.200.1]
3 11 ms 9 ms 7 ms 10.0.33.2
4 12 ms 12 ms 13 ms 5350043A.cable.casema.nl [83.80.4.58]
5 10 ms 12 ms 14 ms 20ge-chnl.amsix.tc2.leaseweb.net [195.69.144.215]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
If your traceroute looks like the first or third one, and you can't connect to our server, it indeed can be a problem at our side.