Comcast vs. Vonage

Posts: 26 · Posted: Thu Feb 23, 2006 9:54 am Post subject:

hey,

no service announcements at this time.

Can vonage tell us if the problem is fixed?

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

shidokan wrote:

hey,

no service announcements at this time.

Can vonage tell us if the problem is fixed?

At present I am not seeing the packet loss that I have seen the previous 2 days.

Hopefully the issue is resolved but I doubt we'll hear what the problem was or how it was fixed.

Posts: 199 · Vonage Forum Master Joined: Mar 26, 2005 Posts: 199

My girlfriend and I both have Vonage and Comcast and live in different areas of Denver. We both have issues. Especially if we are downloading or uploading. Voice quality goes bad. Comcast cast has 6600 down and 384 up. I find this odd.

Posts: 409 · Posted: Thu Feb 23, 2006 11:11 am Post subject:

whatever went on with this service issue it has left my phone unable to stay connected just like last time this service issue was announced.

I sure would like to know what keeps happening.

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

SBMongoos wrote:

My girlfriend and I both have Vonage and Comcast and live in different areas of Denver. We both have issues. Especially if we are downloading or uploading. Voice quality goes bad. Comcast cast has 6600 down and 384 up. I find this odd.

Are you using a router that supports QoS? Comcast can't do anything about you clobbering your own bandwidth.

Posts: 409 · Posted: Thu Feb 23, 2006 5:13 pm Post subject:

March 09, 2005

Vonage Being Blocked -- Again

Company says "new instance" of service outages in the Midwest seems to indicate a port-blocking incident.

By Paul Kapustka Advanced IP Pipeline

Vonage Holdings Corp. said it is investigating new potential incident of its Voice over IP service being blocked, this time by a cable television company that also provides Internet services.
Brooke Schulz, Vonage's vice president for corporate communications, confirmed that the company is "investigating a new instance" of service interruption that appears to be another case of port blocking. Schulz said the incident involves Vonage customers who use high-speed Internet services provided by a cable operator, somewhere in the Midwest U.S.

Last week, the Federal Communications Commission reached a consent decree with Madison River Communications of Mebane, N.C., under which Madison River agreed to pay the government $15,000 for its action of trying to block Vonage's service, and to never block Vonage's VoIP service in the future.

Over the past two weeks, industry sources who declined to be named said they had heard rumors that some Vonage customers in the Midwest were having their services blocked. On Wednesday, Schulz confirmed that Vonage is "investigating an instance [of service outages] on a cable operator's system in the Midwest."

Vonage declined to name the operator. Schulz said that Vonage does not yet know the exact number of customers affected, but that it could range "from the tens to the hundreds to the thousands." Schulz said that Vonage was able to re-establish service for several customers who complained by rerouting its VoIP traffic.

Unlike the Madison River incident, Vonage has not voiced any complaint about the new incident to the FCC, Schulz said.

"We are still investigating, and expect to have more facts next week," Schulz said. "But we are taking this very seriously."

FIRST TIME I READ THIS and its dated 2005

Posts: 274 · Vonage Forum Master Joined: Feb 09, 2006 Posts: 274

How coincidental that my Comcast Internet was down from around 2:00 p.m. CST to 11:30 p.m. CST today. In the 2 years I've had Comcast high speed Internet, the longest outage I had was probably an hour or two.

And it figures it happened on a day where I had some very important files to Email. Evil or Very Mad

Posts: 409 · Posted: Fri Feb 24, 2006 11:22 am Post subject:

I caved in this morning and called Vonage in my very last attempt to fix this dropped call issue I'm left with each time a comcast/vonage service issue is going on.

I contacted Executive Support, Explained all what was going on with my services in a condensed form. This was verified when He looked into my account.

I asked Him what last thing I could try before giving in and cancelling. Since switching isp was not an option
(there is no other cable service my aera)
I am being sent out a replacement router at no charge since this has been going on since April 2005.

We both will be monitoring whats going on from a brand new router. This will assure in the monitoring any router issues are not happening.

I will keep records from ping, speed.. tests and vonage will be monitoring my router. Hopefully being armed with this information if anymore issues arise it will be helpful in entering into a battle with my isp

Guess Im in for the long haul now.

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

After a good day yesterday now I'm back to:

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

Request timed out.
Request timed out.
Request timed out.
Reply from 216.115.22.200: bytes=32 time=84ms TTL=113
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.115.22.200: bytes=32 time=67ms TTL=113
Request timed out.
Reply from 216.115.22.200: bytes=32 time=63ms TTL=113
Request timed out.
Reply from 216.115.22.200: bytes=32 time=52ms TTL=113
Reply from 216.115.22.200: bytes=32 time=69ms TTL=113
Request timed out.
Request timed out.
Reply from 216.115.22.200: bytes=32 time=70ms TTL=113

Ping statistics for 216.115.22.200:
Packets: Sent = 17, Received = 6, Lost = 11 (64% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 84ms, Average = 23ms

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

1 * * * Request timed out.
2 13 ms 13 ms 12 ms 68.86.119.65
3 14 ms 14 ms 14 ms 68.87.230.105
4 13 ms 14 ms 14 ms 68.87.230.250
5 18 ms 16 ms 16 ms 12.125.194.13
6 19 ms 18 ms 33 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 18 ms 18 ms 19 ms att-gw.chi.gblx.net [192.205.32.126]
9 * * 70 ms Vonage-Holdings-Corp-Vonage-Toll-Free-NWRK.ge-2-
3-0.403.ar1.NYC1.gblx.net [64.210.19.18]
10 * * * Request timed out.
11 * 51 ms 63 ms 216.115.22.200

Trace complete.

Sure looks to me like the problem is between att-gw.chi.gblx.net and Vonage-Holding-Corp-Vonage-Toll-Free-NWRK.ge-2-3-0.403.ar1.NYC1.gblx.net

Posts: 409 · Posted: Fri Feb 24, 2006 11:38 am Post subject:

att has a known issue when tracing or pinging even on the dsl broadband boardband reports forum. It doesnt affect voip on my side though.

Is your voip quality bad now, or is it just your tests that are bad?