| Very high latency My test results:
»/linequality/nil/2242170
My problem:
»www.techsupportforum.com/network···st947535
Please also follow the links in that post. I would greatly appreciate any help/advice. I think Blizzard is done helping me and I don't think my isp wants to admit this is their problem. I am good with computer software but not so much with networking. I need to arm myself with knowledge before I start this battle with my isp. Thanks ahead of time for your help. |
|
|
|
 heels_fan1.20.09 The start of SocialismPremium
join:2003-02-07
Columbia, TN
kudos:1 | do another tracert to google or somewhere and see if you get the same response.
Also, do you know of any other customers on the same ISP?
--
Take your hatred of our Government out of the Technical Forums! |
|
| Thanks for the response.
Tracing route to www.l.google.com [64.233.167.147]
over a maximum of 30 hops:
1 34 ms 15 ms 15 ms 10.1.1.1
2 14 ms 23 ms 13 ms open9.tvscable.com [12.169.32.78]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 50 ms 41 ms 37 ms py-in-f147.google.com [64.233.167.147]
Trace complete. |
|
| lol www.l.google.com
Where did the l come from? I didn't put it there. Anyway.... |
|
1 edit | Btw I'm a Kentucky fan. You'll still help me right?  |
|
heels_fan1.20.09 The start of SocialismPremium
join:2003-02-07
Columbia, TN
kudos:1 | said by Ganji:Btw I'm a Kentucky fan. You'll still help me right? I wont hold that against you!
anyways, I think that there could be a problem with your ISPs connection to their backbone provider (ATT). Her is a traceroute from my router to your ISPs router. I am also on an ATT connection.
1 12.116.114.77 [AS 7018] 20 msec 20 msec 20 msec
2 tbr2.ormfl.ip.att.net (12.122.106.66) [AS 7018] [MPLS: Label 31120 Exp 0] 48 msec 48 msec 48 msec
3 tbr1.attga.ip.att.net (12.122.12.121) [AS 7018] [MPLS: Label 31500 Exp 0] 48 msec 52 msec 48 msec
4 tbr2.dtrmi.ip.att.net (12.122.10.197) [AS 7018] [MPLS: Label 31599 Exp 0] 48 msec 48 msec 52 msec
5 gar1.dtrmi.ip.att.net (12.122.82.233) [AS 7018] 48 msec 48 msec 52 msec
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
I also went to nwtools.com and did a traceroute back to your ISPs router. It made it fine as you can see:
»nwtools.com/default.asp?prog=tra···69.32.78
TraceRoute to 12.169.32.78 [open9.tvscable.com]
Hop (ms) (ms) (ms) IP Address Host name
1 1 1 0 66.98.244.1 gphou-66-98-244-1.ev1servers.net
2 0 0 0 66.98.241.16 gphou-66-98-241-16.ev1servers.net
3 0 0 0 66.98.240.10 gphou-66-98-240-10.ev1servers.net
4 1 1 4 38.112.25.21 g0-3.na21.b015619-0.iah01.atlas.cogentco.com
5 110 7 2 38.112.36.49 t4-3.mpd01.lax05.atlas.cogentco.com
6 7 6 7 154.54.5.201 p14-0.core02.dfw01.atlas.cogentco.com
7 7 6 6 154.54.2.98 t3-3.mpd01.dfw01.atlas.cogentco.com
8 7 7 6 154.54.6.94 vl3491.mpd01.dfw03.atlas.cogentco.com
9 7 7 8 154.54.5.189 g15-0-0.core01.dfw03.atlas.cogentco.com
10 7 7 6 192.205.32.253 -
11 38 38 38 12.123.16.206 tbr2.dlstx.ip.att.net
12 37 37 38 12.122.10.89 tbr1.sl9mo.ip.att.net
13 37 37 37 12.122.12.185 tbr1.dtrmi.ip.att.net
14 37 37 37 12.123.208.25 gar1.dtrmi.ip.att.net
15 54 54 54 12.169.32.78 open9.tvscable.com
--
Take your hatred of our Government out of the Technical Forums! |
|
 JeepMattC'mon the UPremium
join:2001-12-28
Wilmington, DE
kudos:2
 ·Verizon FiOS
| I make it okay to your 12.x.x.x router as well - wow, your gateway is 10.1.1.1?? Man, that must be a small ISP! 
1 2 ms 2 ms Berwyn.home [192.168.1.1]
2 5 ms 5 ms L100.VFTTP-21.PHLAPA.verizon-gni.net [72.78.214.1]
3 7 ms 5 ms P6-0.LCR-03.PHLAPA.verizon-gni.net [130.81.96.36]
4 6 ms 7 ms [130.81.29.108]
5 6 ms 10 ms 0.so-6-0-0.XL1.PHL6.ALTER.NET [152.63.3.77]
6 11 ms 10 ms 0.so-0-0-0.XL1.IAD8.ALTER.NET [152.63.36.25]
7 10 ms 10 ms 0.so-6-0-0.BR1.IAD8.ALTER.NET [152.63.32.157]
8 13 ms 12 ms [204.255.169.2]
9 39 ms 38 ms tbr1.wswdc.ip.att.net [12.123.8.98]
10 39 ms 39 ms tbr2.phlpa.ip.att.net [12.122.2.86]
11 38 ms 40 ms tbr1.dtrmi.ip.att.net [12.122.10.37]
12 38 ms 37 ms [12.122.82.225]
13 58 ms 58 ms open9.tvscable.com [12.169.32.78]
--
"ONE team - ONE city - ONE dream!!" |
|
1 edit | So heels fan says might be problem with my isp's connection to att. But then you both post 2 good tracert's. So maybe I'm missing something here but what do I do next? What do I tell my isp? Sorry for my noobishness 
Edit: Also how do I respond to my isp when they have already told me,
AFTER THAT 2ND HOP IT LEAVES OUR SYSTEM AND IS ON SPRINTS BACK BONE. ANY LATENCY AFTER THAT HOP IS UP TO THE PROVIDER CONNECTED TO SPRINT. We cant guarantee anything once it leaves our system. |
|
 burner50Helping Darwin WINPremium,VIP
join:2002-06-05
Cowtown
kudos:1
 ·inmotionhosting
| reply to Ganji
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Me>tracert 12.169.32.78
Tracing route to open9.tvscable.com [12.169.32.78]
over a maximum of 30 hops:
1 * 242 ms 2 ms 192.168.1.1
2 35 ms * 21 ms 10.16.0.1
3 19 ms 12 ms 11 ms 12-215-13-1.client.mchsi.com [12.215.13.1]
4 20 ms 17 ms 20 ms 12-215-4-22.client.mchsi.com [12.215.4.22]
5 27 ms 24 ms 25 ms tbr2.cgcil.ip.att.net [12.123.6.62]
6 28 ms 25 ms 27 ms tbr2.dtrmi.ip.att.net [12.122.10.133]
7 27 ms 200 ms 181 ms gar1.dtrmi.ip.att.net [12.123.208.29]
8 90 ms 79 ms 71 ms open9.tvscable.com [12.169.32.78]
Trace complete.
I think it is att's problem. Unfortunatley there is not much you can do about it, your isp has to start bitching to AT&T
--
Semi Trailers belong on Rail cars |
|
| Ok, thanks so much for all the information. I guess I'll try my isp again and I'm going to see if I can get dsl in my area since AT&T has it for $10 per month now. If you didn't know about the $10 per month dsl you can read about it here:
»www.boston.com/business/technolo···ell_Pos3 |
|
JeepMattC'mon the UPremium
join:2001-12-28
Wilmington, DE
kudos:2 Reviews:
·Verizon FiOS
| Ganji-
Burner may have made a good trace there. Looks like there may be some peak-time overload on your ISP - which is common.
It would take alot of persistence for them to communicate with ATT on that matter.
--
"ONE team - ONE city - ONE dream!!" |
|
