No response from au.voxalot.com - unable to register!

[VoipAlot]

What's going on? Our office has not been able to register for some time??? We all hold Voxalot PRO plans.

Could anyone offer some insight or if they are too experiencing issues (again)?

We've recently had a smooth run with Voxalot - so I am surprised they are playing up again!

Everything else works! We can directly register with other VSP's including: Pennytel, MyNetFone, iiNet, Exetel, MyTel, FaktorTel, etc.

:S

C:\>ping au.voxalot.com
Pinging au.voxalot.com [202.60.88.238] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 202.60.88.238:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


C:\>ping voxalot.com
Pinging voxalot.com [72.51.47.59] with 32 bytes of data:
Reply from 72.51.47.59: bytes=32 time=191ms TTL=52
Reply from 72.51.47.59: bytes=32 time=193ms TTL=52
Reply from 72.51.47.59: bytes=32 time=193ms TTL=52
Reply from 72.51.47.59: bytes=32 time=192ms TTL=52

Ping statistics for 72.51.47.59:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 191ms, Maximum = 193ms, Average = 192ms


C:\>ping google.com.au
Pinging google.com.au [66.102.11.104] with 32 bytes of data:
Reply from 66.102.11.104: bytes=32 time=30ms TTL=58
Reply from 66.102.11.104: bytes=32 time=29ms TTL=58
Reply from 66.102.11.104: bytes=32 time=28ms TTL=58
Reply from 66.102.11.104: bytes=32 time=29ms TTL=58

Ping statistics for 66.102.11.104:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 30ms, Average = 29ms

[VoipAlot]

I found a web site on the internet that allowed you to PING both I.P. and host name addresses:

VOXALOT.COM

Please Note: voxalot.com is ALIVE! (166 ms)

AU.VOXALOT.COM

Warning: fsockopen() [function.fsockopen]: unable to connect to au.voxalot.com:80 (No route to host) in /ping.php on line 5

Attention! au.voxalot.com is DOWN! (No route to host)

EU.VOXALOT.COM

Please Note: eu.voxalot.com is ALIVE! (301 ms)

US.VOXALOT.COM

Please Note: us.voxalot.com is ALIVE! (254 ms)

[VoipAlot]

C:\>tracert au.voxalot.com

Tracing route to au.voxalot.com [202.60.88.238]
over a maximum of 30 hops:

  1     5 ms     4 ms     4 ms  192.168.1.1
  2    28 ms    27 ms    28 ms  230.223.11.169
  3    27 ms    27 ms    27 ms  231.225.233.122
  4    29 ms    29 ms    28 ms  am8.pipenetworks.com [211.100.223.131]
  5    33 ms    29 ms    29 ms  br2.e3networks.com.au [121.22.213.93]
  6    49 ms    47 ms    48 ms  xr1.bne.dedicatedservers.net.au [118.127.9.188]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
...
...
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

[Bedlore]

Experiencing the same issue here. Can we please have information on what's happening and when you expect it to be fixed by.

Thanks

[VoipAlot]

I still have Martin's direct telephone number. I was tempted to call him. I just don't understand why things should be so difficult!

What is wrong with Communication?
Announcements / RSS / Something!

[martin]

Investigating now.

[martin]

Seems like routes into the Brisbane data centre are down. I have raised a support ticket and will advise on the status ASAP.

[martin]

Latest update is server is shorting out Technicians are looking at it now.

[Bedlore]

Martin, Why don't you get automatically notified on an outage? The voxalot website status knew about the outage (stating that "A limited set of users may be experiencing some di", limited in the sense to everyone in Australia I guess) so why the extensive delay in investigation.

Can we also have an ETA on return of service please?

[martin]

The data centre have advised that the server needs to be replaced. This is happening this morning. I will call them to get an update.