SG Broadband Community

I am willing to call as much as i got to, or whatever because i really want this fixed because i really use to love my Cox@Home but lately it hasnt been what it should be at all. Not even close. Been having the service for 2 years +
With paying from $45 to $50 a month for this is just not fair because you know why rise the price when you arent going to get the same speed or better for paying more. Doesnt make sense. But anyone out there that can help me please please do. I am willing to do anything to get this problem fixed. I mean does anyone out there work for Cox@Home in louisiana, work for @Home in general , a big CEO of @Home, anyone important out there that deals with @Home, anyone that works out there for above.net routers, or above.net in anyway? I am trying to find everyone and anyone who can help me. I been waiting 6 to 8 months for getting these other problems fixed and i think they had lots of time. Also on there website Cox@Home in louisiana they say they are contantly proactively upgrading. But i dont think thats the case because this would have not happened.

Please reply
Any help is very appreicated


Tracing route to www.download.com [64.124.237.148]
over a maximum of 30 hops:


2 44 ms 87 ms 60 ms 10.68.3.129
3 20 ms 56 ms 109 ms 10.83.128.49
4 79 ms 12 ms 30 ms c1-pos9-1.nworla1.home.net [24.7.78.109]
5 106 ms 32 ms 41 ms c1-pos3-0.atlnga1.home.net [24.7.65.194]
6 49 ms 46 ms 135 ms c1-pos2-0.washdc1.home.net [24.7.65.209]
7 1142 ms 1154 ms 1155 ms above-athome-oc3.iad.above.net [209.249.203.81]

8 1110 ms 1112 ms 1154 ms core1-core3-oc48.iad1.above.net [209.249.203.34]

9 1177 ms 1189 ms 1171 ms sjc2-iad1-oc48.sjc2.above.net [216.200.127.26]
10 1212 ms 1225 ms 1206 ms sfo1-sjc2-oc48-2.sfo1.above.net [208.184.232.54]

11 1190 ms 1185 ms 1194 ms main2colo78-core1-oc48.sfo1.above.net [208.184.2
28.10]
12 1201 ms 1280 ms 1185 ms 209.133.66.13.above-gw2.cnet.com [209.133.66.13]

13 1220 ms 1225 ms 1188 ms abv-sfo1-redirect.cnet.com [64.124.237.148]

Trace complete.



Tracing route to www.techtv.com [208.185.233.134]
over a maximum of 30 hops:


2 10 ms 9 ms 38 ms 10.68.3.129
3 73 ms 159 ms 20 ms 10.83.128.49
4 46 ms 19 ms 18 ms c1-pos9-0.nworla1.home.net [24.7.72.85]
5 37 ms 45 ms 22 ms c1-pos3-0.atlnga1.home.net [24.7.65.194]
6 56 ms 42 ms 84 ms c1-pos2-0.washdc1.home.net [24.7.65.209]
7 1103 ms 1106 ms 1113 ms above-athome-oc3.iad.above.net [209.249.203.81]

8 1116 ms 1110 ms 1221 ms core1-core3-oc48.iad1.above.net [209.249.203.34]

9 1200 ms 1220 ms 1205 ms sjc2-iad1-oc48.sjc2.above.net [216.200.127.26]
10 1199 ms 1277 ms 1203 ms main1colo4-core3-oc12.sjc2.above.net [208.184.21
0.162]
11 1206 ms 1177 ms 1194 ms 64.124.32.151.e-media.com [64.124.32.151]
12 1193 ms 1196 ms 1187 ms www.zdtv.com [208.185.233.134]

Trace complete.



Look at how much my first hop changes it should be 10ms or less
Plus 2nd hop shouldnt be that high either or 3rd.
Also the 1000 ms + is very bad too.




SpeedGuide.net TCP/IP Analyzer Results


TCP options string = 020405b401010402

MTU = 1500
MTU is fully optimized for broadband.

MSS = 1460
Maximum useful data in each packet = 1460, which is equal to MSS.

Default Receive Window (RWIN) = 64240
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 64240
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)

bandwidth * delay product:
Your RcvWindow limits you to: 2569.6 kbps (321.2 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1027.84 kbps (128.48 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 118 hops
TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349)= 00000000

Same answer as you got on DSL reports.

No.

@Home is bankrupt, it will not get fixed anytime soon.

Kip

Thats not true.
Our DL speed on AT&T in Seattle got bumped from 1.5mbit/sec to 6.5 mbit/sec on Friday !!!!

I would be worried with you 6 and 7 position hops.

Notice #7 is with above.net. You need to call them. It could be @Home problem communicating to above.net but @home won't listen to you. They will say it is above.net's prob;em.

I see this quite often on my service, with the first above.net service, about every 3 months.

Anyhow, call support @ above.net and explain to them the first hop out of the @home service and into an above.net server is a problem. What this does is #1 gets above.net to look at it right away and they will tell you if it's their problem and #2 if it's @homes problem, they will call @home because @home pays for the above.net bandwidth they use.

Good luck

heres email addresses and phone numbers

http://www.above.net/company/cntct_io.html

what up coonass

man i can't believe you are still having this problem from the last time i saw you posting in here (well maybe i can with all that been goin on)

anyway i saw in dslreports you said you were callin 1-800-234-3993 to get to cox

well you might try callin 1-800-794-2635 it was the last # i had to call to cox Baton Rouge direct from tier2

man when i first saw you in here i told you it might take them time like 3-4 months to straighten out the problem, takes time to dig a trench and lay/light fibre, but that was when i thought @Home had a chance to make it

now im thinkin you might want to check out the DSL in coonass country

take it easy coonass if that # don't get you any results hit me up and i might give you a super top secret # where the person on the other end actually picks up a phone not a call on a headset que :2cool:

RodRod, you're not the man!

His problem isn't with @Home.
It is with Above.net

I'm near seattle and look at my trace that goes through @home Wash DC on a different server.

Host Name IP Address Hop Ping Time
* Unknown Host * 192.168.0.1 1 0ms
* Unknown Host * 10.85.186.1 2 14ms
r1-ge4-1.sttls1.wa.home.net 24.9.59.209 3 14ms
* Unknown Host * 10.0.220.149 4 14ms
c1-pos6-2.sttlwa1.home.net 24.7.76.185 5 14ms
c1-pos3-0.lnmtco1.home.net 24.7.64.6 6 41ms
c1-pos1-0.chcgil1.home.net 24.7.65.149 7 55ms
c1-pos3-0.clevoh1.home.net 24.7.64.174 8 55ms
c1-pos2-0.cmdnnj1.home.net 24.7.65.237 9 82ms
c1-pos2-0.bltmmd1.home.net 24.7.65.222 10 83ms
c2-pos1-0.washdc1.home.net 24.7.65.89 11 82ms
wbb1-pos3-0.pop1.va.home.net 24.7.74.218 12 82ms
core1.paix-e.ea.com 64.232.139.10 13 83ms
POS0-0.core1.abn-iad.ea.com 159.153.224.254 14 69ms
fert02.abn-iad.ea.com 159.153.224.11 15 82ms
* Unknown Host * 159.153.226.24 16 83ms


I dont see 1000ms after I leave WashDC @ home, but then again, I'm not going through his problem spot @ above.net.

Don't listen to HotRod69 or whatever he claims to be.

He'll only get you mad.

Call above.net and explain the problem to them.

I see the exact same problem when my routes leave @home SanJose CA, and use above.net, from time to time..... And you'll get much further when talking with above.net.

RodRod5 is worse than a Tier 1 tech who still has a job ! All he likes to do is complain about other people and how @home sucks, no wonder he doesn't have a tech support job anymore. (if he has a new one, it won't last with his attitude!)

For DaveM:

1) Rodrod5 is a regular and competent contributor. There will be no inappropriate, offensive criticism on this board.

2) The problem IS with @Home. The circuit is question is one which @Home purchases to connect with above.net

3) We've been over this ground repeatedly, both here and at DSLReports. Intim83 has started and posted the same information to many threads. He claims to expect that a bankrupt company will upgrade an OC# or install another one in a matter of "hours or days". Lots of people have told him it won't happen. The postings are getting close to spam.

Kip

Tracing route to http://www.download.com [64.124.237.148]
over a maximum of 30 hops:

1 10 ms 10 ms 10 ms
2 10 ms 10 ms 10 ms
3 20 ms 20 ms 30 ms 167.142.157.29
4 30 ms 20 ms 20 ms pionet-bordercore1-ether1.pionet.net [216.248.90.62]
5 30 ms 30 ms 20 ms ins-bordercore2-t3-0-1-1.desm.netins.net [167.142.51.17]
6 40 ms 40 ms 40 ms aads.above.net [206.220.243.71]
7 40 ms 40 ms 41 ms core1-core2-oc3.ord1.above.net [216.200.254.89]
8 50 ms * 40 ms core2-ord1-oc48.ord2.above.net [208.185.0.202]
9 131 ms 130 ms 130 ms sjc2-ord2-oc48.sjc2.above.net [208.184.233.45]
10 120 ms 130 ms 130 ms core3-core4-oc48.sjc2.above.net [208.184.102.197]
11 130 ms 120 ms 140 ms sfo1-sjc2-oc48-2.sfo1.above.net [208.184.232.54]
12 140 ms 120 ms 120 ms main2colo78-core1-oc48.sfo1.above.net [208.184.228.10]
13 130 ms 120 ms 130 ms 209.133.66.13.above-gw2.cnet.com [209.133.66.13]
14 130 ms 131 ms 140 ms abv-sfo1-redirect.cnet.com [64.124.237.148]

This is what I got. You might want to try again.

Originally posted by Kip Patterson
For DaveM:

1) Rodrod5 is a regular and competent contributor. There will be no inappropriate, offensive criticism on this board.

2) The problem IS with @Home. The circuit is question is one which @Home purchases to connect with above.net

3) We've been over this ground repeatedly, both here and at DSLReports. Intim83 has started and posted the same information to many threads. He claims to expect that a bankrupt company will upgrade an OC# or install another one in a matter of "hours or days". Lots of people have told him it won't happen. The postings are getting close to spam.

Kip

thanks kindly for the nice words KIP

i would expect that eventually @Home will make the upgrades (or ATT if it comes to that) but it will take time

the Sacremento, Ca. issue and the KC, MO. issue like this took about 3/5 months to resolve

it takes time

i told the coonass to wait it out before to avoid all the troubles of the switch over to DSL, but now with all of @Homes problems their subs might go through the pain and hassle of an ISP switch without their choice :2cool:

Originally posted by DaveM

RodRod5 is worse than a Tier 1 tech who still has a job ! All he likes to do is complain about other people and how @home sucks, no wonder he doesn't have a tech support job anymore. (if he has a new one, it won't last with his attitude!)

1. I loved @Home and Stream and still do it is the stupid MSOs i hate now

2. What is your solution to the issue...............

3. Even if it was an above.net issue or an @Home and Above issue it will still take time to solve they obviously need a fatter pipe and it will not come in over night no matter who pays and how much they pay to do it

4. People who dont know me and are clutching for straws always say i must have been this or that type of employee but they are wrong i was loved and respected and sat on the mentor line and was loved there as well

5. I am hated by a few fools in here that A. are more worried about being "THE MAN" instead of solving problems and cant take the fact that they dont know it ALL about EVERYTHING B. Want people to continue to waste their time and effort to call in for a know issue that is being worked on just so @Home has to waste support time and effort on it C. people who are MSO butt kissers that lie to people and tell them the transition from @Home to another provider will go smoother than greases goose crap through a tin horn...........it wont we all have seen the past post about cable MSO/ISP transitions :2cool:

Unacceptable posting removed by moderator.

What was so unacceptable?
Email me why you deleted the post.
I was telling the truth.
And you are censoring it!!!

See what I posted here!!!
https://www.speedguide.net/forums/ ... adid=52748

You have withheld your email address from this forum and declined to accept PM.

I warned you earlier about personal attacks, and you continued them in two more messages.

Your technical contributions are welcome.

Kip

End of thread.

I sent you an email, you can see I was reporting an attack of defamation. Not creating one.