Comcast vs. Vonage

Posts: 1123 · Vonage Forum **MVM** Joined: May 26, 2005 Posts: 1123

Oh yeah, you're right. That's how forgettable the two are, that I confused them. Very Happy

Posts: 159 · Vonage Forum Master Joined: Aug 05, 2005 Posts: 159

Problem is back this morning. I am seeing close to 50% packet loss between att-gw-chi.gblx.net and vonage-holdings-corp-vonage-toll-free-nwrk.ge-2-3-0.ar1.nyc1.gblx.net.

Tracing route to vonage.com [216.115.22.200]
over a maximum of 30 hops:
[font=Courier New]
1 <1 ms <1 ms <1 ms 192.168.2.1
2 1 ms <1 ms <1 ms 192.168.1.1
3 * * * Request timed out.
4 11 ms 11 ms 16 ms 68.86.117.237
5 11 ms 11 ms 9 ms 68.87.230.45
6 9 ms 9 ms 26 ms 68.87.231.89
7 13 ms 9 ms 9 ms 68.87.230.250
8 10 ms 11 ms 13 ms 12.125.194.9
9 13 ms 11 ms 11 ms tbr2-p012001.cgcil.ip.att.net [12.123.4.230]
10 10 ms 11 ms 11 ms gbr7-ge20.cgcil.ip.att.net [12.123.6.25]
11 11 ms 11 ms 11 ms att-gw.chi.gblx.net [192.205.32.126]
12 41 ms 57 ms 50 ms vonage-holdings-corp-vonage-toll-free-nwrk.ge-2-
3-0.403.ar1.nyc1.gblx.net [64.210.19.18]
13 61 ms 45 ms * 10.31.3.253
14 52 ms * * 216.115.22.200
15 * * 42 ms 216.115.22.200

Trace complete.[/font]

Posts: 1 · New Forum Member Joined: Mar 06, 2006 Posts: 1

i'm working on a project about the internet, and i'm looking for people who think that their VOIP service was blocked by their internet providers. if anyone has had a similar experience and wants to share it, please contact me off the list at:
madorj@thirteen.org

Posts: 1715 · Posted: Mon Mar 06, 2006 11:36 am Post subject:

Ahh... I was just going to ask if things have changed since this thread has hit some of the mainstream sources (PC Mag,etc)... I know all of my problems have disappeared since late last week. Wasn't able to get my Softphone working on my Comcast Business connection this weekend, but I'm thinking it was my laptop.

Posts: 44 · Full Forum Member Joined: Feb 21, 2006 Posts: 44

It was better for a while. I thought perhaps they actually fixed the problem, but it seems to be back.

Pinging vonage.com [216.115.22.200] with 32 bytes of data:

Request timed out.
Reply from 216.115.22.200: bytes=32 time=53ms TTL=115
Reply from 216.115.22.200: bytes=32 time=54ms TTL=115
Request timed out.
Request timed out.
Reply from 216.115.22.200: bytes=32 time=51ms TTL=115
Request timed out.
Reply from 216.115.22.200: bytes=32 time=45ms TTL=115
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.115.22.200: bytes=32 time=44ms TTL=115
Request timed out.
Request timed out.
Reply from 216.115.22.200: bytes=32 time=49ms TTL=115
Request timed out.
Reply from 216.115.22.200: bytes=32 time=50ms TTL=115
Request timed out.
Request timed out.
Reply from 216.115.22.200: bytes=32 time=52ms TTL=115
Reply from 216.115.22.200: bytes=32 time=52ms TTL=115
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.115.22.200: bytes=32 time=49ms TTL=115
Request timed out.
Request timed out.
Request timed out.
Reply from 216.115.22.200: bytes=32 time=52ms TTL=115
Reply from 216.115.22.200: bytes=32 time=54ms TTL=115
Request timed out.
Reply from 216.115.22.200: bytes=32 time=51ms TTL=115
Request timed out.
Reply from 216.115.22.200: bytes=32 time=50ms TTL=115
Reply from 216.115.22.200: bytes=32 time=53ms TTL=115
Reply from 216.115.22.200: bytes=32 time=52ms TTL=115
Reply from 216.115.22.200: bytes=32 time=49ms TTL=115
Reply from 216.115.22.200: bytes=32 time=51ms TTL=115

Ping statistics for 216.115.22.200:
Packets: Sent = 40, Received = 18, Lost = 22 (55% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 54ms, Average = 22ms

Tracing route to vonage.com [216.115.22.200]
over a maximum of 30 hops:

1 * * * Request timed out.
2 14 ms 11 ms 12 ms ge-1-37-ur01.wchicago.il.chicago.comcast.net [68
.86.119.65]
3 13 ms 14 ms 14 ms 68.87.230.105
4 14 ms 14 ms 14 ms 68.87.230.250
5 16 ms 17 ms 16 ms 12.125.194.13
6 19 ms 18 ms 17 ms tbr1-p011901.cgcil.ip.att.net [12.123.4.226]
7 17 ms 16 ms 16 ms gbr7-ge30.cgcil.ip.att.net [12.123.6.29]
8 19 ms 25 ms 16 ms att-gw.chi.gblx.net [192.205.32.126]
9 * * * Request timed out.
10 * 53 ms 52 ms 10.31.3.253
11 49 ms 51 ms * 216.115.22.200
12 51 ms 50 ms 51 ms 216.115.22.200

Posts: 159 · Vonage Forum Master Joined: Aug 05, 2005 Posts: 159

Ok, didn't want to actually go through the effort but I think I'm going to setup a VPN using hamachi or openvpn (both awesome free software) and reroute my vonage traffic through a friend's non-Comcast connection until this pissing match between the two companies is resolved once and for all. In theory I think this should work as long as his last hop is clean and not barfing packets.

BTW, pingplotter is awesome. I think I am going to buy a copy after my 30 day trial ends. It alerts me immediately as soon as it sees the packet loss on the last mile to Vonage. Also has excellent history recording capabiilities.

Posts: 13 · Vonage Forum Associate Joined: Feb 21, 2006 Posts: 13

I too am having this problem again today. Cry

My original post and findings are still accurate, with the exception that today the outgoing audio quality is fine (my voice) and the incoming audio quality is bad (the person who called me)...
vonage-forum.com/sutra68136.html#68136" target="_blank">http://www.vonage-forum.com/sutra68136.html#68136

Earlier I had latency navigating around secure.vonage.com, it was slow, but at least I could navigate, now (11:55AM) it is completely unreachable. Funny enough I Terminal Server into the datacenter (behind ISP XO) and everything works fine!

This is intentional, there is no other reason for it (perhaps a lazy Comcast tech who has not found or replaced a bad NIC in a router somewhere. At the very least you would think if this is a known problem then they (Comcast) should route traffic around/elsewhere to get to Vonage, that is the whole point of having a router at that level, not to $%#@$^ us over with. This is Comcast's fault - FIX IT!

Canceling service from either company does no good - call Comcast (unfortuantly from your cell phone) and complain!!

Posts: 81 · Vonage Forum Senior Joined: Feb 27, 2006 Posts: 81

I'm working from home today and decided to do my own unscientific test of access to the Vonage Dashboard. I'm a Comcast user and my work laptop I connected directy to the internet via Comcast and went to the log in. Teh first 2 attempts wouldn't even load fully. From the time I hit the submit button on the 3rd, until the last elements on the page loaded was 2:40. I then cleared the cash and closed the browswer and launched my VPN connection *over the same Comcast internet link* to my employer's network. Launched a browser session and logged into the Vonage Dashboard. All elements loaded in 8 seconds. I went back and repeated three times with similar results.

Same computer, same browser configuration, same internet link. In the direct connect case it's Comcast connecting to a Vonage IP address, and in the VPN case it's Comcast connecting to my employer's VPN tunnel device address and our network forwarding out to the Vonage IP.

Like I said at the start, it's not scientific and I'm not a network guy. But it raises some questions in my mind about the validity of it being a Vonage issue an not Comcast playing games with Vonage traffic.

Posts: 44 · Full Forum Member Joined: Feb 21, 2006 Posts: 44

ShelChgo wrote:

Like I said at the start, it's not scientific and I'm not a network guy. But it raises some questions in my mind about the validity of it being a Vonage issue an not Comcast playing games with Vonage traffic.

Did you run a traceroute from both scenarios?

Posts: 1123 · Vonage Forum **MVM** Joined: May 26, 2005 Posts: 1123

D'oh.