eu.voxalot.com dead...
 

eu.voxalot.com appears borked.

I cannot register on it - I can if I point to us.voxalot.com - but both my fxo and fxs ports use different Voxalot accounts on eu - and they are both failing...

working ok (registering) on my side both EU and US servers. I just have now other problems of my own..

Hi guys, all servers are fully operational and working fine.

Erm, not for me.
I rebooted my ATA - no registration (it's showing registration failed)
us working - eu not...

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:

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:

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:

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.

I have no problems using voxalot, but this is what I see when I trace eu.voxalot.com.
Strange?

Tracing route to eu.voxalot.com [85.17.19.194]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 41 ms 40 ms 41 ms proxy01.eu1.voxalot.com [85.17.19.194]

Trace complete.

Some routers/modems or even firewalls seem to cause this kind of behavior. It's usually a 'problem' at the customers side.

Have you tried an online traceroute website like the example below?

Traceroute Visual

Online traceroute websites only show a traceroute from their side, and not from your computer's side.

It's always better to perform a traceroute from your PC, because it shows you whether the problem is occuring at your side, your ISP's side or at our side.

I had realised that but in the majority of cases if it was a problem with your computer/ISP side you would not be able to get to the online website anyway.