Quote:
Originally Posted by g00fy
In my logs I don't see any outage in the connection to eu.voxalot.com. Whole night the registration succeeded. So, it must be a problem elsewhere, I suppose.
Apparently it seems there will be scheduled downtime untill February 1st. It would be nice if Voxalot would inform it's customers when that will happen. They will get the exact date from Leaseweb (may be an admin can confirm that we will get this information in any way? That is, if there is any admin reading this, what I doubt from earlier experiences).
|
Thanks,
It's now 5pm GMT and the eu server is down again! I can ping the us & au with no problem. Again I haven't received any status notification. I think my $25 deserves a response from Voxalot about what's going on!
Here are my ping results
Pinging eu.voxalot.com [85.17.19.194] with 32 bytes of
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 85.17.19.194:
Packets: Sent = 4, Received = 0, Lost = 4 (100% lo
ping us.voxalot.
Pinging us.voxalot.com [64.34.173.199] with 32 bytes o
Reply from 64.34.173.199: bytes=32 time=265ms TTL=55
Reply from 64.34.173.199: bytes=32 time=265ms TTL=55
Reply from 64.34.173.199: bytes=32 time=265ms TTL=55
Reply from 64.34.173.199: bytes=32 time=264ms TTL=55
Ping statistics for 64.34.173.199:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 264ms, Maximum = 265ms, Average = 264ms
ping au.voxalot.
Pinging au.voxalot.com [202.60.88.238] with 32 bytes o
Reply from 202.60.88.238: bytes=32 time=161ms TTL=53
Reply from 202.60.88.238: bytes=32 time=160ms TTL=53
Reply from 202.60.88.238: bytes=32 time=163ms TTL=53
Reply from 202.60.88.238: bytes=32 time=161ms TTL=53
Ping statistics for 202.60.88.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 160ms, Maximum = 163ms, Average = 161ms