Outage? and can't get to secure.voipo.com to open a ticket either

[voipinit]

Is VPanel still having issues? I can't get into the 'contacts' panel (under the features tab). Anyone else?

[scott2020]

Incoming calls on two VOIPo numbers are not going through. My backup SIP trunks are working now. Just getting DISCONNECT messages now calling VOIPo DID's.

I am on central01 and it is showing UNREACHABLE.

About 10 minutes later the phone starts ringing. No failover. I am BYOD, but it shows unreachable or high latency on central01. Tried opening a ticket but not sure if it made it.

Also cannot call out on VOIPo trunk.

[VOIPoTim]

Incoming calls on two VOIPo numbers are not going through. My backup SIP trunks are working now. Just getting DISCONNECT messages now calling VOIPo DID's.

I am on central01 and it is showing UNREACHABLE.

About 10 minutes later the phone starts ringing. No failover. I am BYOD, but it shows unreachable or high latency on central01. Tried opening a ticket but not sure if it made it.

Also cannot call out on VOIPo trunk.

Central01 is not in The Planet. Can you post a traceroute?

[Xponder1]

I checked The Planets own forums and the last update posted a moment ago says "We may have a lead, specific to a certain subnet range. This is still unconfirmed, but the network guys are all on the conference bridge working on different parts."

So in English they dunno what is wrong lol.

I still can not get Google to load. Off topic but is anyone else able to pull up google.com?

[VOIPoTim]

I checked The Planets own forums and the last update posted a moment ago says "We may have a lead, specific to a certain subnet range. This is still unconfirmed, but the network guys are all on the conference bridge working on different parts."

So in English they dunno what is wrong lol.

I still can not get Google to load. Off topic but is anyone else able to pull up google.com?

A specific subnet?

Kind of ironic that that would affect multiple datacenters with thousands of servers in hundreds of IP blocks. That's just my opinion though

[Xponder1]

A specific subnet?

Kind of ironic that that would affect multiple datacenters with thousands of servers in hundreds of IP blocks. That's just my opinion though

Ya thats why I threw in the comment about them not knowing what is wrong.

I was bored so I did a tracert for you note the part in red.

Tracing route to Central01.voipwelcome.com [67.228.251.106]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Access_Denied [192.168.10.1]
2 18 ms 6 ms 8 ms 10.33.128.1
3 9 ms 9 ms 11 ms COX-68-12-8-157-static.coxinet.net [68.12.8.157]

4 10 ms 8 ms 7 ms ge-7-0-1-mx02.mtc1.tul.ok.cox.net [68.12.18.246]

5 9 ms 8 ms 9 ms xe-0-3-0-dsr02.rd.tul.ok.cox.net [68.12.18.4]
6 15 ms 16 ms 14 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
7 158 ms 15 ms 203 ms po-2.r03.dllstx09.us.bb.gin.ntt.net [129.250.4.3
8]
8 15 ms 15 ms 17 ms te1-1.cer01.dal01.dallas-datacenter.com [157.238
.228.10]
9 17 ms 15 ms 16 ms po1.dar02.dal01.dallas-datacenter.com [66.228.11
8.203]
10 38 ms 16 ms 40 ms po2.fcr04.dal01.dallas-datacenter.com [66.228.11
8.218]
11 16 ms 17 ms 17 ms central01.voipwelcome.com [67.228.251.106]

Trace complete.

[burris]

I checked The Planets own forums and the last update posted a moment ago says "We may have a lead, specific to a certain subnet range. This is still unconfirmed, but the network guys are all on the conference bridge working on different parts."

So in English they dunno what is wrong lol.

I still can not get Google to load. Off topic but is anyone else able to pull up google.com?

I have ATT DSL and that the internet was never a problem.

VOIPo had me on East and I went down. I moved to Central and all is well..

[Xponder1]

I have ATT DSL and that the internet was never a problem.

VOIPo had me on East and I went down. I moved to Central and all is well..

Well I promise you that the outage was real.

http://forums.theplanet.com/index.ph...0&#entry601238

[eagle 1]

I also show registration failed from 17:52 to 18:12 est for central01. everything fine now
also timeout for registration from 14:12 to 14:21, then again 14:26 to 14:42
Tracing route to central01.voipwelcome.com [67.228.251.106]
over a maximum of 30 hops:

1 10 ms 8 ms 7 ms wsip-68-99-159-33.ri.ri.cox.net [68.99.159.33]
2 8 ms 7 ms 8 ms clvdcmtb04.cl.ri.cox.net [98.173.132.5]
3 9 ms 6 ms 8 ms ip98-173-132-97.cl.ri.cox.net [98.173.132.97]
4 16 ms 15 ms * chgobbrj01-ae0.r2.ch.cox.net [68.1.0.222]
5 16 ms 18 ms 16 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.98]
6 42 ms 38 ms 43 ms as-1.r21.dllstx09.us.bb.gin.ntt.net [129.250.3.17]
7 * 45 ms 39 ms po-3.r03.dllstx09.us.bb.gin.ntt.net [129.250.4.182]
8 43 ms 41 ms 37 ms te1-1.cer01.dal01.dallas-datacenter.com [157.238.228.10]
9 79 ms 210 ms 42 ms po1.dar01.dal01.dallas-datacenter.com [66.228.118.201]
10 * 43 ms 38 ms po1.fcr04.dal01.dallas-datacenter.com [66.228.118.214]
11 39 ms 42 ms 39 ms central01.voipwelcome.com [67.228.251.106]

Trace complete.

[VOIPoTim]

We're looking into why some people still had a failure. It looks like a few dozen people went down during that time.

We'll post more info later after we've looked into it more.