Curado Kev
Premium
join:2003-12-17
Portage, MI
 ·Charter Pipeline
| ATT Routers slow and SW Michigan - What can we do ??
Well this has been going on for at least 3 weeks and generally during the week from 7pm - 10pm.
I play CSS every night and connect with a server out of Chicago. Whether I ping this server, cnn.com, google.com etc. My latency jumps from 15 to 140 when I hit the ATT routers similar to the graph here in this post:
»Slow in the Great Lakes region?
Then around 10 pm it settles down and my ping goes back to 25 on CSS instead of the high 90-110.
Before you blame my rig or modem etc, let's skip that and tell me how to address bad routers ?? I assume we are all up the creek.
I've had ok dealings with Charter customer service in the past. But since I heard Bay City was closed, I need to get the patience up to call them and deal with some Tier 1 tech that takes me through the same garbage and I'll still never get to talk with a net admin like before.
So anyways, bad routers - Is it worth calling ATT ??
Thanks Kev |
|
norton
join:2005-08-03
Holland, MI | Helpful idea?
have you ever tried to contact a techie at charter through the web chat function? I do this and they respond very quickly. |
|
milbrath
join:2006-03-27
Dresden, TN
| reply to Curado Kev
You actually think you will be able to call AT&T, ha.
The issue more than likely already has an AT&T ticket on it, issued by themselves or by inquiry from a large Tier2 provider(like charter) they will fix it in due time. There is a lot of planning to be done when dropping a core router.
BM |
|
Curado Kev
Premium
join:2003-12-17
Portage, MI
·Charter Pipeline
| reply to Curado Kev
Milbrath I agree 
I assume people (Charter?) would notice this and have a trouble ticket with ATT. I'm sure a Charter VP making 250K year has more pull than a loser CSS player (customer) trying to kill guys on the internet
I was hoping some Netadmin for Charter in Michigan would help us out and check for us. I've had 4 friends with Charter experience the same slowdown in surfing.Of course, CSS players can detect a ping swing quicker than joe blow surfer 
Help me Charter Netadmins and VPs with some clout - LOL
Kev |
|
TF_BioHazard
join:2003-09-21
Janesville, WI | Ive noticed it the past week in janesville,wisconsin. Starting to get really annoyed. And same time as you around 6-7ish till late at night. Anyone else in my area having issues as well? I am contacting charter now. |
|
TF_BioHazard
join:2003-09-21
Janesville, WI
| Ok just got off the phone with tech support michagen and wisconsin areas are experiencing the issue outside of charter. Its all ATT. Even roadrunner is having the same issues we are they route through the same hop through chicago as we do. so we need to get on ATT ASS! |
|
Curado Kev
Premium
join:2003-12-17
Portage, MI
·Charter Pipeline
| reply to Curado Kev
Well it was screwed up tonight again..
Normal ping to Chicago 25ms from Portage,MI. It was 160 from 8:30pm est when I got on until 11:15pm. Now running around 23...
Give me an ATT number and I'll call. But you would think Charter and Roadrunner would be complaining ??
Kev |
|
Flummoxed
Premium
join:2002-01-24
Saint Peters, MO
| I felt the problem from ATT tonight. Playing world of warcraft and all of a sudden 15 people droped from my TS server in VA, all had Charter ISP including me. Took awhile before we could reconnect, couldn't ping but tracert showed after two hops in ATT everything else was timing out. |
|
stivvy
Technonerd
join:2002-05-08
| reply to Curado Kev
I'd love to be able to give you guys an update on this, but we know almost as little as you do when it comes to this issue. At the call center yesterday morning we were experiencing the same high pings and rotten speeds as you were.
The same hop was having issues for us as well and it was reported to our Tech Assurance Center. We received no updates from that time point forward.
Here is my trace from yesterday:
4 5 ms 5 ms 5 ms 24-231-187-177.static.bycy.mi.charter.com [24.231.187.177]
5 5 ms 4 ms 5 ms 24-231-187-109.static.bycy.mi.charter.com [24.231.187.109]
6 8 ms 8 ms 8 ms 24-247-236-218.static.aldl.mi.charter.com [24.247.236.218]
7 10 ms 10 ms 10 ms 24-247-60-62.static.aldl.mi.charter.com [24.247.60.62]
8 389 ms 403 ms 402 ms 12.118.112.21
9 372 ms 371 ms 371 ms tbr1-p012401.dtrmi.ip.att.net [12.123.139.138]
10 368 ms 354 ms 348 ms tbr2-cl19.phlpa.ip.att.net [12.122.10.38]
11 412 ms 411 ms 418 ms tbr1-cl71.phlpa.ip.att.net [12.122.9.165]
You can see that the same ATT hop is causing the issue for us and you.
If I hear anything I'll pass it along. |
|
Curado Kev
Premium
join:2003-12-17
Portage, MI
·Charter Pipeline
| reply to Curado Kev
Thanks Stivy and it has been that way for at least 3 weeks primarily durign the week.
For me , its nice to see it has gotten worse to get the attention of everybody. Otherwise I sit on the phone and bang my head on the wall trying to convince a tech "It's really not spyware!!"
I appreacite any update if you get it 
Thx Kev |
|
milbrath
join:2006-03-27
Dresden, TN
1 edit | Thought I might say one more thing. It may not be AT&T. Here in TN charter has a connection with Level3, does the same thing from time to time,presumably from congestion, it may just be that in your area charter no longer has a large enough pipe with AT&T and what you are seeing is from congestion. Just a thought, I'm sure the problem will be fixed sooner or later. It takes us 30 days to get another T1 provisioned with the telcos, no clue how long it takes charter to get another OC-xx provisioned with AT&T or whomever is involved, but I am sure it's also a good 30 days.
Ideally the ISP will look ahead, but and OC-48(or more than likely far greater say OC-256 depending on how much they need) is quite expensive and they may have held off to long. Hell a T1(1.5mbs) in our area is $625 minimum. I can only imagine what an OC-48 costs. For all you complaining about your paltry 2mb on your 6mb connection try paying what a rural ISP pays per month for less. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| reply to TF_BioHazard
AT&T Worldnet will not listen to you; you are not their customer. They are providing peering to providers, and they will only listen to the providers with the peering contracts. All that you can do is rag on your provider, and let them push the problem up to the peering provider.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Curado Kev
Premium
join:2003-12-17
Portage, MI | reply to Curado Kev
Don't get excited, believe me I'm not. But it looks good tonight. If it last a month,then I'll get excited.
CKev |
|
TF_BioHazard
join:2003-09-21
Janesville, WI | they were ok till now, god ATT sucks ass. all att hops over 300 again. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| Patience. The old AT&T ran Worldnet as a backbone, and SBC ran their own backbone operation: SBC Global.
Since the merger, SBC adopted the name AT&T, and is in the process of combining the backbone branches of the business. It has been only nine months, or so, since the merger took effect. I expect that all backbone operations will be consolidated under one business unit, by which time AT&T (the new version, former SBC) should have ironed out a lot of kinks. Until then, your own network ops will have to deal with AT&T because they are the AT&T customer, not you.
09/14/06 17:42:50 Slow traceroute 24-231-187-177.static.bycy.mi.charter.com
Trace 24-231-187-177.static.bycy.mi.charter.com (24.231.187.177) ...
192.168.102.1 RTT: 0ms TTL:170 (Chihiro ok)
192.168.0.1 RTT: 0ms TTL:170 (Suzuka ok)
69.227.43.254 RTT: 14ms TTL:170 (adsl-69-227-43-254.dsl.pltn13.pacbell.net ok)
64.164.97.66 RTT: 0ms TTL:170 (dist1-vlan50.pltn13.pbi.net ok)
151.164.43.54 RTT: 14ms TTL:170 (bb1-g3-0.pltnca.sbcglobal.net ok)
151.164.190.85 RTT: 14ms TTL:170 (bb1-p3-0.crsfca.sbcglobal.net ok)
151.164.41.10 RTT: 14ms TTL:170 (ex1-p14-0.eqsjca.sbcglobal.net ok)
12.122.79.101 RTT: 14ms TTL:170 (gar7-p390.sffca.ip.att.net bogus rDNS: host not found [authoritative])
12.122.85.134 RTT: 68ms TTL:170 (No rDNS)
12.122.10.5 RTT: 83ms TTL:170 (tbr1-cl1.cgcil.ip.att.net bogus rDNS: host not found [authoritative])
12.122.9.134 RTT: 82ms TTL:170 (tbr2-cl22.cgcil.ip.att.net bogus rDNS: host not found [authoritative])
12.122.10.133 RTT: 55ms TTL:170 (tbr2-cl18.dtrmi.ip.att.net bogus rDNS: host not found [authoritative])
12.122.12.182 RTT: 69ms TTL:170 (gbr2-p100.dtrmi.ip.att.net bogus rDNS: host not found [authoritative])
12.123.208.29 RTT: 69ms TTL:170 (gar1-p370.dtrmi.ip.att.net bogus rDNS: host not found [authoritative])
12.124.15.62 RTT: 137ms TTL:170 (No rDNS)
24.247.60.61 RTT: 138ms TTL:170 (24-247-60-61.static.aldl.mi.charter.com ok)
24.247.236.217 RTT: 151ms TTL:170 (24-247-236-217.static.aldl.mi.charter.com ok)
24.231.187.177 RTT: 164ms TTL:238 (24-231-187-177.static.bycy.mi.charter.com ok)
P.S. 164ms to Michigan from California is not good; should be closer to 69ms, or so.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Curado Kev
Premium
join:2003-12-17
Portage, MI
·Charter Pipeline
| reply to Curado Kev
Norman,
We have patience - sort of- but only if this was always a problem. However, it has cropped up right around end of August and has not gone away.
Maybe they turned the keys over or got rid of the one person who knew how to run it correctly. Maybe the person retired - LOL
Thanks for your input, CKev |
|
Techno1961
@charter.com
| Saw this after i posted another thread. I'm having same issues. Ping rate from Birmingham Alabama Charter to ATT Atlanta GA good, but once it hits AT&T, rate jumps 10x. Use to get 30ms. Now I'm getting booted off of game servers for having a too high ping rate.
Culprit is in AT&T at 12.118.120.9.
I see others experiencing same problem. Not just an isolated incident. Friends here also with Charter going to same server seein issue too.
Tracing route to 8.9.4.50 over a maximum of 30 hops
1 1 ms 1 ms 1 ms local-192-168-1-1.local.lan [192.168.1.1]
2 9 ms 19 ms 11 ms ts2c3-0-10ldsal.lds.al.charter.com [10.105.224.1
]
3 9 ms 8 ms 9 ms cr1srp1-0ldsal.lds.al.charter.com [24.177.176.97
]
4 18 ms 10 ms 9 ms er1ge2-0ldsal.lds.al.charter.com [24.196.0.1]
5 104 ms 107 ms 104 ms 12.118.120.9
6 138 ms 135 ms 131 ms tbr1-p012201.attga.ip.att.net [12.123.20.178]
7 129 ms 128 ms 127 ms tbr2-cl17.wswdc.ip.att.net [12.122.10.69]
8 124 ms 123 ms 125 ms sar1-a360s3.wswdc.ip.att.net [12.123.8.117]
9 129 ms 124 ms 127 ms so-8-0-0.car3.Washington1.Level3.net [4.68.127.1
53]
10 127 ms 125 ms 126 ms ae-2-54.bbr2.Washington1.Level3.net [4.68.121.97
]
11 146 ms 154 ms 143 ms as-2-0.bbr2.Chicago1.Level3.net [209.247.10.129]
12 336 ms 224 ms 229 ms ae-24-52.car4.Chicago1.Level3.net [4.68.101.40]
13 147 ms 165 ms 148 ms 4.79.66.146
14 135 ms 142 ms 148 ms 8.9.4.50
Trace complete. |
|
Rampage522
join:2001-10-18
Birmingham, AL | I was also seeing similar dropoffs in response time once getting off the same hardware device on the traceroute posted above, but this was Wednesday night. I did not have an opportunity to test Thursday night. |
|
Zappa2000
join:2001-12-16
Kalamazoo, MI
| reply to Curado Kev
Hmm.. I just tried that ip, and I get:
4 21 ms 21 ms 20 ms 71-13-66-1.static.aldl.mi.charter.com [71.13.66.
1]
5 49 ms 29 ms 30 ms 12.124.15.105
6 37 ms 36 ms 35 ms gbr1-p70.dtrmi.ip.att.net [12.123.208.26]
7 35 ms 34 ms 34 ms tbr2-p012501.dtrmi.ip.att.net [12.122.12.177]
8 38 ms 37 ms 38 ms tbr2-cl18.cgcil.ip.att.net [12.122.10.134]
9 33 ms 32 ms 33 ms ggr2-p390.cgcil.ip.att.net [12.123.6.37]
10 36 ms 50 ms 36 ms 192.205.33.210
11 35 ms 36 ms 36 ms 4.79.66.146
12 36 ms 22 ms 21 ms 8.9.4.50
Which is pretty good... |
|
TF_BioHazard
join:2003-09-21
Janesville, WI | From maybe 2am-8pm its always been good. ITs 8pm till around 2am it sucks ass cause ATT pipes are either full or the routers are sucking ass and need to be replaced. |
|
