SG Broadband Community

Something is going on here. All of a sudden after a long time of good service, everyone's @Home connection has gone to hell. High pings to the gateway, low bandwidth downloading... it's all happened suddenly to users across the country.

When I call @Home though, either locally or nationally, they act like this is a new problem. I tell them that I know other people across the nation are having the same thing and they just seem to ignore that. They are sending a tech out to "tune the connection" but I think it's just more smoke to cover the real problem.

I have already signed up for Telocity DSL. My bandwidth may never hit the 1MB/s I got a month ago on cable, but I doubt I would see that with @Home again anyways. If ANYONE has information as to what is going on... please let us know here.

I agree, same problem here.. Cnat play games any more, pings exceed 150 MS - 600MS on CABLE! I do better on dialup. I have Adelphia Powerlink...

Good luck with Telo****ty, I signed up as well and I was on Step 2 for 4 weeks. My line was never provisioned. So I canceled. Besides Northpoint is about to go out of buisiness. I canceled!

Something's up, got up one morning and 200KBytes slower, I didn't do anything, just gone

I lost my great speeds about 2 weeks ago. @home has sent a tech out the house and could'nt find anything except a weak signal.

He finally came clean, @home is up to some repairs, upgrades, and most people in my area are suffering for it. He claimed that everything should be up to normal in a couple of weeks.

I don't believe a word he said, @home is going to lose a few customers if they don't get speeds back to normal. Somedays I only get a tad better than dial-up......this sucks big time for the $$$$$$$$$$ it cost.

man, i thought i was the only one

same thing here on AT&T@Home, it's been slow recently, slow response times and loading times, and pings are horrid

everybody bombared @home with emails concerning this slowness, we must make them fix it, after all we DO pay for this service that at the moment isn't serviing!

If is any consolation, I have been experiencing the same for the last 3 weeks and now -- just today -- am back up in the 2 - 2.6 MB range.

Excite@home
Alexandria VA

But Mr. John, you got de Lord on your side

i have powerlink! it rulez! : w00t w00t
23 ping on my fav game servers and 400k dl's on high band websites yea but i do think @home is up to something. I heard that it was the ****e b4 i got cable. then suddenly everyones sux

[ 02-26-2001: Message edited by: sabre81 ]

That national problem is probably individual problems. Has anyone done any traceroutes to see where the problem is. I bet it is some overloaded circuits that @HOME needs to upgrade. BTW, my speeds have not changed since we had an upgrade in our circuit abot 3 months ago. They are faster than they were a year ago.

No, it is not individual problems, yes all has been checked, it is a @home problem, be happy yours is cool

My connection is only good between the hours of 2:30am-7:00am Too bad it's the only thing available in my area

SEE BELOW......

[ 02-27-2001: Message edited by: BMED ]

First 100 matches for search of 48183 home.com..
Showing ZIP 48183 home.com - back to all domains
.
who Day Zip ISP Test
Result User
Has Hour
(NYC) dom
27th 48183 @home 1300/50 15 wodhvn1.mi.home.com
26th 48183 @home 1192/467 500/128 07 taylor1.mi.home.com
27th 48183 @home 1116/35 16 wodhvn1.mi.home.com
14th 48183 @home 945/169 22 wodhvn1.mi.home.com
15th 48183 @home 628/118 19 wodhvn1.mi.home.com
bmed 23rd 48183 @home 473/95 13 taylor1.mi.home.com
zdoggy 23rd 48183 @home 446/127 19 taylor1.mi.home.com
bmed 27th 48183 @home 442/101 19 taylor1.mi.home.com
26th 48183 @home 412/132 13 taylor1.mi.home.com
25th 48183 @home 321/121 11 taylor1.mi.home.com
16th 48183 @home 294/125 100/100 16 taylor1.mi.home.com

These speeds suck!

Below are the speeds from the very near past….

http://www.geocities.com/sammiepuppy/DSLReports10092000.jpg

http://www.geocities.com/sammiepuppy/PCPitstop.jpg

I cried today!


[ 02-27-2001: Message edited by: BMED ]

DaveM,
The 3rd HOP is the router in the Headend. At least it is in my case. Maybe the local office has an overloaded router in the Headend. Mayeb they are getting rid of an oler router and installing a new CISCO. Some of the older markets run the 3COM system. The newer ones like mine run with the CISCO equipment. Just a few ideas. BTW, if the router is overload, @HOME can tell. They monitor the routers usage and load per upstream port. On the brightside, IT CAN ONLY GET BETTER!!!

Here is a before & after tracert that might help explain why the mid-west USA was having problems.Man It's been a nightmare here in Illinois. Everything is hunkydorry now.... :-)
Reply from 206.204.83.2: bytes=32 time=73ms TTL=249

Ping statistics for 206.204.83.2:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 73ms, Average = 51ms

C:\WINDOWS>tracert www.madonion.com

Tracing route to www.madonion.com [206.204.83.2]
over a maximum of 30 hops:

1 14 ms * 23 ms bb1-fe1-0.moline1.il.home.net [24.2.218.1]
2 51 ms * * c1-se10-9.chcgil1.home.net [24.7.75.25]
3 21 ms 29 ms * c2-pos10-0.chcgil1.home.net [24.7.77.170]
4 * 25 ms * aadsnap1.noc.conxion.net [206.220.243.75]
5 * 54 ms * decocis-01-pos20.conxion.net [206.204.250.98]
6 181 ms 139 ms 153 ms svcacis-04-pos53.conxion.net [206.204.250.101]
7 * 69 ms 166 ms svcamadonion1.conxion.com [206.204.11.85]
8 72 ms * 71 ms www.madonion.com [206.204.83.2]

Trace complete.

C:\WINDOWS>


Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1999.

C:\WINDOWS>tracert www.madonion.com

Tracing route to www.madonion.com [206.204.83.2]
over a maximum of 30 hops:

1 21 ms 31 ms 25 ms bb1-fe1-0.moline1.il.home.net [24.2.218.1]
2 26 ms 27 ms 22 ms c1-se10-9.chcgil1.home.net [24.7.75.25]
3 27 ms 26 ms 28 ms c2-pos10-0.chcgil1.home.net [24.7.77.170]
4 25 ms 31 ms 17 ms aadsnap1.noc.conxion.net [206.220.243.75]
5 60 ms 54 ms 58 ms decocis-01-pos20.conxion.net [206.204.250.98]
6 70 ms 74 ms 74 ms svcacis-04-pos53.conxion.net [206.204.250.101]
7 76 ms 74 ms 75 ms svcamadonion1.conxion.com [206.204.11.85]
8 74 ms 81 ms 74 ms www.madonion.com [206.204.83.2]

Trace complete.

C:\WINDOWS>

I've noticed that my pings are different. My pings to my gateway used to be pretty consistant but recently have gotten more erratic.

#1Echo Reply, ttl=254, 77 ms
#2Echo Reply, ttl=254, 33 ms
#3Echo Reply, ttl=254, 63 ms
#4Echo Reply, ttl=254, 12 ms
#5Echo Reply, ttl=254, 18 ms
#6Echo Reply, ttl=254, 38 ms
#7Echo Reply, ttl=254, 60 ms
#8Echo Reply, ttl=254, 24 ms
#9Echo Reply, ttl=254, 53 ms
#10Echo Reply, ttl=254, 23 ms

Statistics: Out 10, in 10, loss 0%, times (min/avg/max) 12/40/77 ms

My third hop is NOT my gateway.
My gateway is no longer in my traceroutes.

There is something else acting as a gateway for me!!!!

But my true gateway no longer is in my traceroutes.

WINIPCFG reports my gateway at 24.20.47.1

My third hop is 24.9.59.209

As a gateway, that is an invalid address, because its not in my same IP grouping !!!!

I ping my gateway 24.20.47.1 at 10MS consistent.

I ping the false gateway 24.9.59.209 At 150-220ms during primtime 6pm to midnight.

People from the outside ping my return gateway 24.9.59.222 at a substantial slowdown compared to the hop right before it, the next previous hop to them.
If the hop right before this IP to them is 50ms, this return gateway will be at 200 to 300ms with substantial packetloss. Again this only happens during primetime.

up until 6:12pm today there was abolutely no issues. I could download 3 5meg files at the same time all averageing 2.5 Mbits/second.

At 6:15pm this dropped to 787Kbit each per second for the three.

But the funny thing is one file download it at 787Kbits and I start a second and it gets the same speed and I start a third and it gets the same speed.

There is a limiting server on our line.

Whatever it is doing, its doing it based on the amount of connections transfering data. It has nothing to do with the server being overloaded.

The day before my Real Gateway disapeered from my traceroutes, everything was fine.
The next evening my traceroutes had a new fake gateway and this crap began. This was the second week in January for me.

By the way my third hop is called r1-fe1-7-100bt-sttls1.wa.home.net

The "100bt" is a 100baseT computer connection. a 100Base T computer could not be used as a gateway as it would be clogged immediately. If this is my new gateway, there is a deffinate reason as to why during primetime we have the slowdown.

But the couldn't just serve a community with a 100BT connection.... could they? Thats suicide!

[ 02-27-2001: Message edited by: DaveM ]

Nothing wrong with @home in Denver yet

AT&T@Home in Portland, OR is 701 Kbps.

The people who have the problem are affected by the third hop away from their system.

Not only is the outpond a problem, so is the inbound server that is three hops away.

Ive done comparisons and the third hop both directions causes problems.

If a buddy on DSL traceroutes me, he's at 50ms average until he hits that hop right before my modem, so my modem IP and my computer IP are slow to him.

Some cities are not yet affected.

Such as spokane washington.

The cities that have DOCSIS enabled servers are affected !!!!

You can tell if you have DOCSIS enabled servers by running a traceroute.

Your second hop will be a 10.xx.xx.xx number, thats your modems IP address and your third hop will be a slow server.

The third hope is not your assigned gateway server. Sometime recently you lost your assigned gateway server in your traceroutes. and the Docsis server took its place.

Yes your gateway server in your network propeties says one thing, but its no longer in your traceroutes.

Not all cities have the problem.

however, nationaaly, @HOME introduce the problem during the month of January.

I complained enough that they gave me a free month of service.

But I call them every couple days and they acknowledge the problem. But I can't get any real info out of them.

It starts around 5pm and stops at midnight.

Like they introduce the DOCSIS slowdown.

The network isn't jammed because pings from the outside world to any ip address in my city suffer and pings to any of my neighbors don't suffer.

Its the traffic on that third hop thats the problem, but I don't think its the traffic... I think its the inability of the DOCSIS to funtion correctly.

DaveM,
That 3rd HOP looks like a circuit. Here is what I received from a traceroute: | 24.9.59.209 | r1-fe1-7-100bt.sttls1.wa.home.net | Seattle, WA, USA |
----------------------------------------------------------------------

Could all this be related to @home rolling out their cable based telephone service...this has been the Cox@home new war cry here in Nawlin's. They are wrapping up the beta testing on their phone service... Could this be tied in to the degraded internet service?

Don't know but my @Home is pretty garbage right now. Everything on the download is fine. The uploads have just gone to crap in the past 2 weeks. I hope they didn't cap lower the cap on me!

[ 03-01-2001: Message edited by: AAF Striker ]

Having Cable @ DSL speed "SUCKS". @home SUCKS.......tell your neighbors not to buy!

I was driving home today and noticed a billboard stating that "56K is for Wimps", Comcast@home will change that. BS,BS,BS, Comcast@home will only take your money and run right now!

[ 03-01-2001: Message edited by: BMED ]

i am quite happy with my ATT@HOME 500-700KB dls and 48-70KB uploads

I ahve noticed a huge slow down in the time my pages load. It started a few weeks ago, one day I got up and my pages were loading very slowly; I thought it would get better later....still waiting!

Soooooo Slow. 70kps.
This is nuts, for the past month my speed has been going down. I have had the new "shaw" out 4 times. They have had lots of excuses and no reasons. They also aren't willing to credit my account. I can get higher connection with my 56K modem.
What the heck is going on? Maybe back to ADSL as they are offering no connection charge right now.

Hmmmm I have @home and my speeds are 2.3Mb dl(of course depending on server). I hope we don't have that problem soon. *sniff*

Originally posted by sabre81:
i have powerlink! it rulez! : w00t w00t
23 ping on my fav game servers and 400k dl's on high band websites yea but i do think @home is up to something. I heard that it was the ****e b4 i got cable. then suddenly everyones sux

[ 02-26-2001: Message edited by: sabre81 ]

ME 2 I LUV MY POWERLINK! But for the last 4 days it has been terrible, never happened to me before, hows yours running now?

I have the same problem with @home now. It started about 1-2 weeks ago. Look at this ping to my gateway that I did today at 4:30pm.

Pinging 24.150.16.1 with 32 bytes of data:

Reply from 24.150.16.1: bytes=32 time=460ms TTL=255
Reply from 24.150.16.1: bytes=32 time=180ms TTL=255
Request timed out.
Reply from 24.150.16.1: bytes=32 time=110ms TTL=255
Reply from 24.150.16.1: bytes=32 time=130ms TTL=255
Reply from 24.150.16.1: bytes=32 time=230ms TTL=255
Reply from 24.150.16.1: bytes=32 time=761ms TTL=255
Reply from 24.150.16.1: bytes=32 time=290ms TTL=255
Reply from 24.150.16.1: bytes=32 time=231ms TTL=255
Reply from 24.150.16.1: bytes=32 time=450ms TTL=255
Request timed out.
Reply from 24.150.16.1: bytes=32 time=171ms TTL=255
Reply from 24.150.16.1: bytes=32 time=150ms TTL=255
Reply from 24.150.16.1: bytes=32 time=70ms TTL=255
Reply from 24.150.16.1: bytes=32 time=380ms TTL=255
Reply from 24.150.16.1: bytes=32 time=381ms TTL=255
Reply from 24.150.16.1: bytes=32 time=200ms TTL=255
Reply from 24.150.16.1: bytes=32 time=260ms TTL=255
Reply from 24.150.16.1: bytes=32 time=260ms TTL=255
Reply from 24.150.16.1: bytes=32 time=491ms TTL=255
Reply from 24.150.16.1: bytes=32 time=191ms TTL=255
Reply from 24.150.16.1: bytes=32 time=140ms TTL=255
Reply from 24.150.16.1: bytes=32 time=191ms TTL=255
Reply from 24.150.16.1: bytes=32 time=130ms TTL=255
Reply from 24.150.16.1: bytes=32 time=160ms TTL=255
Reply from 24.150.16.1: bytes=32 time=160ms TTL=255
Reply from 24.150.16.1: bytes=32 time=150ms TTL=255
Reply from 24.150.16.1: bytes=32 time=110ms TTL=255
Reply from 24.150.16.1: bytes=32 time=160ms TTL=255
Reply from 24.150.16.1: bytes=32 time=201ms TTL=255
Reply from 24.150.16.1: bytes=32 time=130ms TTL=255
Reply from 24.150.16.1: bytes=32 time=341ms TTL=255
Reply from 24.150.16.1: bytes=32 time=160ms TTL=255
Reply from 24.150.16.1: bytes=32 time=200ms TTL=255
Reply from 24.150.16.1: bytes=32 time=90ms TTL=255
Reply from 24.150.16.1: bytes=32 time=190ms TTL=255
Reply from 24.150.16.1: bytes=32 time=220ms TTL=255
Reply from 24.150.16.1: bytes=32 time=90ms TTL=255
Reply from 24.150.16.1: bytes=32 time=211ms TTL=255
Reply from 24.150.16.1: bytes=32 time=270ms TTL=255
Reply from 24.150.16.1: bytes=32 time=271ms TTL=255
Reply from 24.150.16.1: bytes=32 time=460ms TTL=255
Reply from 24.150.16.1: bytes=32 time=130ms TTL=255
Reply from 24.150.16.1: bytes=32 time=300ms TTL=255
Reply from 24.150.16.1: bytes=32 time=290ms TTL=255
Reply from 24.150.16.1: bytes=32 time=150ms TTL=255
Reply from 24.150.16.1: bytes=32 time=130ms TTL=255
Reply from 24.150.16.1: bytes=32 time=201ms TTL=255
Reply from 24.150.16.1: bytes=32 time=190ms TTL=255

Ping statistics for 24.150.16.1:
Packets: Sent = 49, Received = 47, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 761ms, Average = 220ms

I am also having the same problems with cgocable. Heres my pings to my DNS.
Ping - Saturday, March 03, 2001 22:01:09


#1 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 105 ms
#2 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 141 ms
#3 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 142 ms
#4 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 150 ms
#5 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 143 ms
#6 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 118 ms
#7 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 134 ms
#8 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 142 ms
#9 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 102 ms
#10 dhcp2.cgocable.net (24.226.1.42): Echo Reply, ttl=251, 129 ms

Statistics: Out 10, in 10, loss 0%, times (min/avg/max) 102/130/150 ms

I am wondering if its the cable modems? I have a (white) InfoRanger SCM-100R that i believe is DOCSIS v1.0

When i called the tech he asked if I had a "grey or white" InfoRanger. I am thinking that the grey has the new DOCSIS v1.1 and @home has upgraded to DOCSIS v1.1 The understanding is that v1.1 is backwards compatible with v1.0 but i am not sure that its not without problems? If anyone is using the Inforanger SCM-110R (grey) could post their ping times also, so maybe we could see if its accaully the version of DOCSIS that is screwing us over?

With all of this national @home outages, slowness, etc. a criminal case could be set up against them. They are basically taking your money for crap. I siggest @home users should ban together and start up a criminal complaint against @home. All the while your paying $40 bucks for 56 k while other ISP's (Roadrunner, Adelephia, etc) are paying $40 for bradband internet. @Home is misleading the public about their services and need to be faught in court for it. They don't have the right to steal your money like that. @Home needs to go down!

my @home went out for almost a week i was pist i never noticed it slowing down it just went out and stoped workin it took me 2 days to get my dail up workin but after the down time i have noticed that speeds semed to almost double and i have had less problems but does ne 1 know wut exactly happened? if so give me a e-mail at pimptrizkit@home.com thanx .... and ne 1 know how many e-mail adress u can have with the @home.com tag????

God! Until I read this message, I thought that only my region was affected! I'm in south Jersey, and I'm getting like 200ms pings consistantly. The only reason I got @Home was to have a decent ping along with nice download speeds. Now I have neither. I'm seriously looking into DSL.

The techs are no help. They assume that we're lying, don't have any real authority anyway, and on the off occasion that they DO send someone out, the person just confirms what I know, suggests some linework, and leaves.

I've asked to speak to a supervisor, and they told me one would return my call in 24-48 hours. Twice.

I have yet to recieve a call.

Aside from the 200 pings, I'm also getting a spike of 14% packetloss every minute or two, at regular intervals, but company line states that there's no problem unless your ping is 400+ and your PL is 20%+. 400MS AND 20%!!! This is outrageous!!!

I'm ready to get DSL, I'm just waiting until tomorrow when I'm done with my last 24-48 Hour waiting period so I can attempt to demand an IMMEDIATE audience with a supervisor, providing that one exists. Kinda like the wizard of Oz. Only a bad router is behind the curtain...

Ugh...

I guess they don't bother about the calls about ping times at their normal levels just when there at 400+ they consider bad cuz they know about the damn problem and have yet to fix it.

-----------------------------------------------------------------------------------
| Hop |IP Address |Location | | ms |Network |
-----------------------------------------------------------------------------------
| 0 |x.x.x.x ... | | |(private use) |
| 1 |x.x.x.x | ... | | 9 |(private use) |
| 2 |10.0.211.17 | ... | | 8 |(private use) |
| 3 |24.7.74.165 | Phoenix, AZ, USA | | 0 |@Home Network |
| 4 |24.7.65.129 | Lamesa, TX, USA | | 20 |@Home Network |
| 5 |24.7.65.126 | Dallas, TX, USA | | 25 |@Home Network |
| 6 |24.7.70.214 | Redwood City, CA 94063 | | 30 |@Home Network |
| 7 |152.63.100.218 | Dallas, TX, USA | | 30 |UUNET Technologies, Inc.|
| 8 |152.63.10.13 | Dallas, TX, USA | | 30 |UUNET Technologies, Inc.|
| 9 |152.63.7.62 | Toronto, ON, Canada | | 112 |UUNET Technologies, Inc.|
| 10 |152.63.128.37 | Toronto, ON, Canada | | 110 |UUNET Technologies, Inc.|
| 11 |152.63.129.34 | Toronto, ON, Canada | | 116 |UUNET Technologies, Inc.|
| 12 |205.150.159.46 | Hamilton, ON, Canada | | 115 |UUNET Canada Inc. |
| 13 |209.167.168.66 | Toronto, ON, Canada | | 117 |UUNET Canada Inc |
| 14 |24.226.0.49 | ?(Canada) | | 66 |Cogeco Cable Solutions |
| 15 |24.150.16.1 | ?(Canada) | | 70 |Cogeco Cable Solutions |
-----------------------------------------------------------------------------------
VisualRoute Report for 24.150.16.1 produced at 8:30 PM on March 4, 2001.
Roundtrip time to 24.150.16.1 (24.150.16.1) average = 70ms min = 60ms max = 80ms

Cogeco looks to be fine... The UUNet seems to be the problem...