Time Warner Bright House Insight Latency

Technical Support
1 2 3 5 Next
We've detected an issue with some Time Warner, Bright House, and Insight customers, and we need some additional information to resolve this issue.

Please post the following information if you are a Time Warner, Bright House, or Insight customer, and you're lagging or seeing high latency in game:

1) A Trace Route
2) A pathping
3) Your location (City, State)
4) If you're wired or wireless
5) The make and model of your router and modem.

Once you've pasted your trace into a post, select and highlight everything you just pasted, and hit the "pre" button (It says "Code Blocks" when you hover your mouse over it). That'll make the information much more readable. Thanks for your help!

Edit (4/18):
I've just received word that we've found the source, location, and nature of the issue. There's no estimate for when this will be fixed, but we are continuing to escalate this issue to get it fixed faster.

Please continue to post your trace route and pathpings as you've done. The more information and data we have, the faster we can get this fixed. Thanks again for posting everything we've asked for!

Edit (4/22):
Thanks to the hard work of our network team and our internet service partners - we can confidently report that we expect this issue to be resolved within the next 8 days =)

Edit (4/30):
This issue has been resolved as of 4/25. Our internet service partners will also be adding additional capacity, which should prevent this from happening again.

Thank you very much for all of the information you've provided, and thank you for your patience!
________________________________________________
Monday - Friday, 8 am - 5 pm PST
I'm not a time warner customer, but I'm having the same issue running thru the att.net hops so i thought i'd link my traceroute:

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 42 ms 40 ms * hlrn-dsl-gw01.hlrn.qwest.net [207.225.112.1]
3 * 39 ms 39 ms hlrn-agw1.inet.qwest.net [71.217.188.1]
4 75 ms 74 ms * lap-brdr-03.inet.qwest.net [67.14.22.78]
5 125 ms 73 ms * 63.146.27.102
6 119 ms * 117 ms cr2.la2ca.ip.att.net [12.122.84.70]
7 116 ms * 117 ms cr1.slkut.ip.att.net [12.122.30.29]
8 119 ms 159 ms 120 ms cr2.dvmco.ip.att.net [12.122.30.26]
9 * 120 ms 153 ms cr1.cgcil.ip.att.net [12.122.31.86]
10 * 121 ms 127 ms cr1.cl2oh.ip.att.net [12.122.2.206]
11 118 ms 120 ms 118 ms cr2.cl2oh.ip.att.net [12.122.2.126]
12 * 146 ms 119 ms cr2.phlpa.ip.att.net [12.122.2.210]
13 139 ms 135 ms * gar1.pitpa.ip.att.net [12.122.107.85]
14 121 ms * 241 ms 12.122.251.2
15 124 ms * * mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20


Initiating out of a Denver suburb, i believe centurylink/qwest to by the isp.
We've detected an issue with some Time Warner customers, and we need some additional information to resolve this issue.

Please post the following information if you are a Time Warner customer, and you're lagging or seeing high latency in game:

1) A [url="http://us.battle.net/support/en/article/performing-a-traceroute?utm_source=internal-support_forums&utm_medium=posting&utm_campaign=BlizzardCS&utm_content=041613"]Trace Route[/url]
2) A [url="https://us.battle.net/support/en/article/running-a-pathping-test?utm_source=internal-support_forums&utm_medium=posting&utm_campaign=BlizzardCS&utm_content=041613"]pathping[/url]
3) Your location (City, State)
4) If you're wired or wireless
5) The make and model of your router and modem.

Once you've pasted your trace into a post, select and highlight everything you just pasted, and hit the "pre" button (It says "Code Blocks" when you hover your mouse over it). That'll make the information much more readable. Thanks for your help!
________________________________________________
Monday - Friday, 8 am - 5 pm PST


Trace and Path below..
Henderson, NC
Hard Wired direct to TWC provided modem
Motorola SBG6580 Modem


Tracing route to 12.129.222.185 over a maximum of 30 hops

1 35 ms 27 ms 23 ms twdp-174-109-144-001.nc.res.rr.com [174.109.144.1]
2 12 ms 16 ms 14 ms a-rtr2-10gig0-2-0-1.2124.nc.rr.com [66.26.46.129]
3 18 ms 19 ms 20 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2]
4 29 ms 31 ms 31 ms 107.14.19.48
5 23 ms 25 ms 24 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
6 * * * Request timed out.
7 32 ms 31 ms 31 ms 192.205.36.217
8 109 ms 114 ms 110 ms cr1.attga.ip.att.net [12.122.84.114]
9 112 ms 109 ms 110 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 132 ms 112 ms 111 ms cr2.la2ca.ip.att.net [12.122.28.178]
11 109 ms 108 ms 108 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 * 110 ms 107 ms 12.122.251.190
13 109 ms 108 ms 110 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


And the Pathping


Tracing route to 12.129.222.185 over a maximum of 30 hops

0 Jeremy-PC [192.168.0.2]
1 twdp-174-109-144-001.nc.res.rr.com [174.109.144.1]
2 a-rtr2-10gig0-2-0-1.2124.nc.rr.com [66.26.46.129]
3 ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2]
4 107.14.19.48
5 ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
6 Vlan557.icore1.A56-Atlanta.as6453.net [209.58.44.53]
7 192.205.36.217
8 cr1.attga.ip.att.net [12.122.84.114]
9 cr2.dlstx.ip.att.net [12.122.28.174]
10 cr2.la2ca.ip.att.net [12.122.28.178]
11 gar29.la2ca.ip.att.net [12.122.129.241]
12 12.122.251.190
13 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Jeremy-PC [192.168.0.2]
0/ 100 = 0% |
1 12ms 0/ 100 = 0% 0/ 100 = 0% twdp-174-109-144-001.nc.res.rr.com [174.109.144.1]
0/ 100 = 0% |
2 15ms 0/ 100 = 0% 0/ 100 = 0% a-rtr2-10gig0-2-0-1.2124.nc.rr.com [66.26.46.129]
0/ 100 = 0% |
3 22ms 0/ 100 = 0% 0/ 100 = 0% ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2]
0/ 100 = 0% |
4 30ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.48
0/ 100 = 0% |
5 26ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
0/ 100 = 0% |
6 29ms 0/ 100 = 0% 0/ 100 = 0% Vlan557.icore1.A56-Atlanta.as6453.net [209.58.44.53]
2/ 100 = 2% |
7 34ms 2/ 100 = 2% 0/ 100 = 0% 192.205.36.217
98/ 100 = 98% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.attga.ip.att.net [12.122.84.114]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.122.28.174]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.28.178]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.190
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]

Trace complete.
Recovery, there appears to be issues early on in your trace. I would show this to your ISP. Thanks!

Thank you for posting your traces, Reportthis.
________________________________________________
Monday - Friday, 8 am - 5 pm PST
I am a Time Warner Customer and I am still having latency issues.

Tracing route to 206.16.235.117 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 13 ms 34 ms 14 ms gi15-0-0-3101.gnboncsg-rtr2.triad.rr.com [24.28.225.189]
4 14 ms 12 ms 12 ms 24.93.64.58
5 19 ms 22 ms 22 ms 107.14.19.48
6 23 ms 17 ms 17 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 * * * Request timed out.
8 30 ms 22 ms 21 ms 192.205.36.217
9 46 ms 43 ms 45 ms cr1.attga.ip.att.net [12.122.84.114]
10 40 ms 46 ms 40 ms cr2.wswdc.ip.att.net [12.122.1.174]
11 39 ms 40 ms 44 ms gar3.ascva.ip.att.net [12.122.113.89]
12 38 ms 39 ms 38 ms 12.122.251.198
13 41 ms 42 ms 42 ms mdf004c7613r0002-tge-12-1.wdc1.attens.net [63.240.197.190]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Tracing route to 201-016-235-117.static.ctbctelecom.com.br [201.16.235.117]
over a maximum of 30 hops:
0 <name>-Spare.Belkin [192.168.10.8]
1 * * *
Computing statistics for 0 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 <name>-Spare.Belkin [192.168.10.8]

Trace complete.


I am on a wired conncetion. My modum is a Time Warner Arris Modem and my router is a Belkin Router. I live near Greensboro NC.

Hope you guys can figure out what's wrong. The lag is quite frustrating.
Raleigh, NC
ASUS NT66R
TWC
Ubee Modem
Wired connection, Checksum Offload off
Frequent disconnects



tracert 63.240.104.93

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms www.asusnetwork.net [192.168.1.1]
2 35 ms 49 ms 27 ms cpe-066-057-048-001.nc.res.rr.com [66.57.48.1]
3 10 ms 11 ms 32 ms ten13-0-0-304.rlghnca-rtr1.nc.rr.com [66.26.44.1
09]
4 13 ms 11 ms 9 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 21 ms 22 ms 23 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 18 ms 19 ms 18 ms 107.14.17.202
7 19 ms 18 ms 18 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.
149]
8 54 ms 58 ms 22 ms 192.205.34.245
9 26 ms 22 ms 26 ms cr1.wswdc.ip.att.net [12.122.88.174]
10 26 ms 26 ms 24 ms cr2.phlpa.ip.att.net [12.122.4.53]
11 119 ms 74 ms 74 ms gar1.pitpa.ip.att.net [12.122.107.85]
12 30 ms 30 ms 30 ms 12-122-254-242.attens.net [12.122.254.242]
13 30 ms 28 ms 28 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.24
0.65.10]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * ^C
Same issue here - new this week or last. Fios ISP but same issues. I think there is a multi-ISP issue, see Tracert again...

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 4 ms 4 ms L100.NYCMNY-VFTTP-247.verizon-gni.net [71.183.246.1]
3 12 ms 7 ms 11 ms G0-5-3-3.NYCMNY-LCR-22.verizon-gni.net [130.81.97.126]
4 10 ms 9 ms 9 ms so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.199.12]
5 7 ms 9 ms 10 ms 0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
6 10 ms * 10 ms 192.205.36.57
7 88 ms 87 ms 87 ms cr2.n54ny.ip.att.net [12.122.86.10]
8 93 ms 96 ms 94 ms cr2.wswdc.ip.att.net [12.122.3.38]
9 98 ms 94 ms 92 ms cr1.attga.ip.att.net [12.122.1.173]
10 93 ms 91 ms 94 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 93 ms 98 ms 96 ms cr1.dlstx.ip.att.net [12.122.1.209]
12 90 ms 96 ms 90 ms cr1.phmaz.ip.att.net [12.122.28.182]
13 91 ms 92 ms 93 ms 12.123.158.5
14 89 ms 87 ms 88 ms 12-122-254-218.attens.net [12.122.254.218]
15 98 ms 215 ms 93 ms mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Raleigh gets much better ping times than up here in Henderson ><

But yea guys keep posting please! Let's get to the bottom of it since Blizz is stepping in to finally help!! Let's play lag free!!!
I live outside of Columbus Ohio, I am a time warner cable customer (and employee if that helps) I have an arris tg 862 mta/modem.
Wired connection.

This is really the first time ive had issues with connections and Time Warner, now i cant stay online for more than a minute with out getting a fatal error.

fatal error im getting is

error #132 (0x85100084) fatal exception!

Program F:\world of warcraft\wow-64.exe
process id: 4364
exception 0xc0000005 (access_violation)

the instruction at "0x0000000076e632d0" referenced memory at "0x0000069ac8aba288".
the memory could not be "read"

Tracert

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms 192.168.0.1
3 * * * Request timed out.
4 21 ms 16 ms 14 ms ae0-1778.cr02.clmcohib.midohio.rr.com [184.59.243.249]
5 24 ms 23 ms 23 ms network-065-029-001-038.midwest.rr.com [65.29.1.38]
6 32 ms 31 ms 48 ms ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
7 26 ms 25 ms 27 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
8 32 ms 28 ms 26 ms ix-17-0.tcore1.AEQ-Ashburn.as6453.net [66.198.154.21]
9 41 ms 44 ms 29 ms if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1]
10 59 ms 58 ms 80 ms 192.205.34.245
11 39 ms 39 ms 39 ms cr2.wswdc.ip.att.net [12.122.84.82]
12 40 ms 39 ms 41 ms cr1.cgcil.ip.att.net [12.122.18.21]
13 35 ms 34 ms 35 ms gar2.clboh.ip.att.net [12.122.133.197]
14 39 ms 37 ms 37 ms 12.122.251.22
15 37 ms 37 ms 37 ms 63.240.130.214
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

pathping:

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Jenn-PC [192.168.1.132]
1 192.168.1.1
2 192.168.0.1
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Jenn-PC [192.168.1.132]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1

Trace complete.
Is this a server side issue or something directly ISP related?
Based on the trace route results provided by others, the issue is with the ATT network not Time Warner Cable. After the connection leaves ‘tbone.rr.com’ (which is the last hop on the Time Warner Cable network) all examples show that the data successfully transitions to the ATT network and then the hops start timing out. I believe this could be related to an off network maintenance being performed since this is commonly seen at night and resumes normal performance during the day time.
If its a Time Warner/ISP issue, I have them working on it. But honestly I cant find anything that suggests its only time warner service or how it could be so selective. Seeing as how its affecting BrightHouse (a time warner affiliate) but not affecting Insight. its strange to me. But none the less, I forwarded it on just to be sure.
as of 12:05pm EST latency in game is starting to spike yet again!


Tracing route to 12.129.222.185 over a maximum of 30 hops

1 71 ms 22 ms 24 ms twdp-174-109-144-001.nc.res.rr.com [174.109.144.1]
2 85 ms 17 ms 12 ms a-rtr2-10gig0-2-0-1.2124.nc.rr.com [66.26.46.129]
3 18 ms 22 ms 18 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2]
4 27 ms 31 ms 31 ms 107.14.19.48
5 25 ms 25 ms 25 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
6 30 ms 35 ms 35 ms Vlan557.icore1.A56-Atlanta.as6453.net [209.58.44.53]
7 23 ms 25 ms 24 ms 192.205.36.217
8 81 ms 78 ms 79 ms cr1.attga.ip.att.net [12.122.84.114]
9 79 ms 80 ms 77 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 81 ms 79 ms 79 ms cr2.la2ca.ip.att.net [12.122.28.178]
11 129 ms 174 ms 92 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 77 ms 76 ms 76 ms 12-122-254-234.attens.net [12.122.254.234]
13 82 ms 77 ms 76 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
I'm a Time Warner Cable customer around Buffalo, NY. I currently am wireless and my modem is a Motorola SB5100.

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms ODINLIGHTNING [192.168.1.1]
2 40 ms 16 ms 14 ms cable-mac1.hmbgny42-ar4001.nyroc.rr.com [69.204.0.1]
3 17 ms 12 ms 12 ms gig1-2-2.buffnyhmb-pe02.nyroc.rr.com [98.0.0.161]
4 26 ms 16 ms 22 ms ae11-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.64]
5 33 ms 37 ms 38 ms bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0.3.3]
6 32 ms 39 ms 34 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
7 33 ms 32 ms 31 ms ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
8 33 ms 34 ms 32 ms 216.1.123.17
9 33 ms 32 ms 33 ms 206.111.2.90.ptr.us.xo.net [206.111.2.90]
10 91 ms 90 ms 90 ms cr2.cgcil.ip.att.net [12.122.81.98]
11 94 ms 91 ms 90 ms cr2.sl9mo.ip.att.net [12.122.2.22]
12 93 ms 93 ms 113 ms cr2.kc9mo.ip.att.net [12.122.28.89]
13 92 ms 88 ms 91 ms cr1.dlstx.ip.att.net [12.122.28.85]
14 96 ms 99 ms 91 ms cr1.phmaz.ip.att.net [12.122.28.182]
15 93 ms 92 ms 90 ms 12.123.158.5
16 239 ms 203 ms 139 ms 12-122-254-218.attens.net [12.122.254.218]
17 124 ms 87 ms 88 ms mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 *



Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 Hoshi.buffalo.rr.com [192.168.1.129]
1 ODINLIGHTNING [192.168.1.1]
2 * cable-mac1.hmbgny42-ar4001.nyroc.rr.com [69.204.0.1]
3 gig1-2-2.buffnyhmb-pe02.nyroc.rr.com [98.0.0.161]
4 ae11-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.64]
5 bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0.3.3]
6 ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
7 ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
8 216.1.123.17
9 206.111.2.90.ptr.us.xo.net [206.111.2.90]
10 cr2.cgcil.ip.att.net [12.122.81.98]
11 cr2.sl9mo.ip.att.net [12.122.2.22]
12 cr2.kc9mo.ip.att.net [12.122.28.89]
13 cr1.dlstx.ip.att.net [12.122.28.85]
14 cr1.phmaz.ip.att.net [12.122.28.182]
15 12.123.158.5
16 12-122-254-218.attens.net [12.122.254.218]
17 mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
18 * * *
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Hoshi.buffalo.rr.com [192.168.1.129]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% ODINLIGHTNING [192.168.1.1]
0/ 100 = 0% |
2 22ms 0/ 100 = 0% 0/ 100 = 0% cable-mac1.hmbgny42-ar4001.nyroc.rr.com [69.204.0.1]
0/ 100 = 0% |
3 14ms 0/ 100 = 0% 0/ 100 = 0% gig1-2-2.buffnyhmb-pe02.nyroc.rr.com [98.0.0.161]
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% ae11-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.64]
0/ 100 = 0% |
5 26ms 0/ 100 = 0% 0/ 100 = 0% bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0.3.3]
0/ 100 = 0% |
6 40ms 0/ 100 = 0% 0/ 100 = 0% ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
0/ 100 = 0% |
7 51ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
0/ 100 = 0% |
8 36ms 0/ 100 = 0% 0/ 100 = 0% 216.1.123.17
0/ 100 = 0% |
9 38ms 0/ 100 = 0% 0/ 100 = 0% 206.111.2.90.ptr.us.xo.net [206.111.2.90]
100/ 100 =100% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.81.98]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.sl9mo.ip.att.net [12.122.2.22]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.kc9mo.ip.att.net [12.122.28.89]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.28.85]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% cr1.phmaz.ip.att.net [12.122.28.182]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% 12.123.158.5
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-218.attens.net [12.122.254.218]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]

Trace complete.
Bright House
Loc : Cocoa, FL.
Modem : Ubee DW3200
Wired Connection

Traceroute :

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 7 ms 7 ms 7 ms 10.108.202.1
2 7 ms 6 ms 7 ms 72-31-193-208.net.bhntampa.com [72.31.193.208]
3 14 ms 13 ms 16 ms 72-31-193-75.net.bhntampa.com [72.31.193.75]
4 20 ms 21 ms 24 ms ten0-10-0-6.orld71-car2.bhn.net [97.69.194.144]
5 22 ms 15 ms 16 ms 72-31-193-191.net.bhntampa.com [72.31.193.191]
6 22 ms 25 ms 21 ms ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
7 25 ms 23 ms 31 ms 107.14.19.36
8 23 ms 26 ms 21 ms 107.14.19.13
9 26 ms 35 ms 36 ms Vlan510.icore1.A56-Atlanta.as6453.net [209.58.44.13]
10 52 ms 51 ms 75 ms 192.205.36.217
11 87 ms 88 ms 88 ms cr2.attga.ip.att.net [12.122.84.150]
12 85 ms 87 ms 85 ms cr1.nsvtn.ip.att.net [12.122.28.106]
13 87 ms 87 ms 91 ms cr2.nsvtn.ip.att.net [12.122.28.70]
14 87 ms 88 ms 87 ms cr1.cl2oh.ip.att.net [12.122.28.74]
15 86 ms 91 ms 83 ms cr1.cgcil.ip.att.net [12.122.2.205]
16 87 ms 133 ms 80 ms gar2.clboh.ip.att.net [12.122.133.197]
17 82 ms 89 ms 82 ms 12.122.251.50
18 88 ms 86 ms 139 ms 63.240.130.210
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Pathping :

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Bithindel-PC [192.168.0.5]
1 10.108.202.1
2 72-31-193-208.net.bhntampa.com [72.31.193.208]
3 72-31-193-75.net.bhntampa.com [72.31.193.75]
4 ten0-10-0-6.orld71-car2.bhn.net [97.69.194.144]
5 72-31-193-191.net.bhntampa.com [72.31.193.191]
6 ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
7 107.14.19.36
8 107.14.19.13
9 Vlan510.icore1.A56-Atlanta.as6453.net [209.58.44.13]
10 192.205.36.217
11 cr2.attga.ip.att.net [12.122.84.150]
12 cr1.nsvtn.ip.att.net [12.122.28.106]
13 cr2.nsvtn.ip.att.net [12.122.28.70]
14 cr1.cl2oh.ip.att.net [12.122.28.74]
15 cr1.cgcil.ip.att.net [12.122.2.205]
16 gar2.clboh.ip.att.net [12.122.133.197]
17 12.122.251.22
18 63.240.130.210
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Bithindel-PC [192.168.0.5]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% 10.108.202.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 72-31-193-208.net.bhntampa.com [72.31.193.208]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 72-31-193-75.net.bhntampa.com [72.31.193.75]
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% ten0-10-0-6.orld71-car2.bhn.net [97.69.194.144]
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% 72-31-193-191.net.bhntampa.com [72.31.193.191]
0/ 100 = 0% |
6 24ms 0/ 100 = 0% 0/ 100 = 0% ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.36
0/ 100 = 0% |
8 24ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.13
0/ 100 = 0% |
9 27ms 0/ 100 = 0% 0/ 100 = 0% Vlan510.icore1.A56-Atlanta.as6453.net [209.58.44.13]
0/ 100 = 0% |
10 30ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.217
100/ 100 =100% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.attga.ip.att.net [12.122.84.150]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr1.nsvtn.ip.att.net [12.122.28.106]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr2.nsvtn.ip.att.net [12.122.28.70]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% cr1.cl2oh.ip.att.net [12.122.28.74]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.2.205]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar2.clboh.ip.att.net [12.122.133.197]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.22
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.210

Trace complete.
Hello. This is for Diablo 3 but I was told to post this here. Time warner cable Roadrunner highspeed internet.

North Charleston, South Carolina.
Wired.
DOCSIS 1.0/1.1/2.0 Compliant Ambiit Broadband
Ubee DDW 2608

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 * * * Request timed out.
2 10 ms 11 ms 11 ms cpe-024-031-209-132.sc.res.rr.com [24.31.209.132]
3 14 ms 13 ms 14 ms ge-3-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.62]
4 21 ms 23 ms 23 ms 107.14.19.48
5 19 ms 19 ms 19 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
6 * * 23 ms Vlan504.icore1.A56-Atlanta.as6453.net [209.58.44.9]
7 20 ms 22 ms 19 ms 192.205.36.217
8 77 ms 74 ms 75 ms cr1.attga.ip.att.net [12.122.84.114]
9 76 ms 75 ms 73 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 73 ms 76 ms 75 ms cr2.la2ca.ip.att.net [12.122.28.178]
11 72 ms 75 ms 71 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 71 ms 75 ms 72 ms 12-122-254-234.attens.net [12.122.254.234]
13 72 ms 71 ms 71 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


For some reason I couldn't get the pingtest to work but here is what it gave me.

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Aaron-PC [192.168.0.11]
1 * * *
Computing statistics for 0 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Aaron-PC [192.168.0.11]

Trace complete.
6:33pm EST and latency in game only is spiking pretty high, here's the latest trace.


Tracing route to 12.129.222.185 over a maximum of 30 hops

1 42 ms 15 ms 20 ms twdp-174-109-144-001.nc.res.rr.com [174.109.144.1]
2 13 ms 12 ms 11 ms a-rtr2-10gig0-2-0-1.2124.nc.rr.com [66.26.46.129]
3 18 ms 37 ms 18 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2]
4 25 ms 31 ms 31 ms 107.14.19.48
5 23 ms 25 ms 25 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
6 37 ms 35 ms * Vlan557.icore1.A56-Atlanta.as6453.net [209.58.44.53]
7 43 ms 24 ms 25 ms 192.205.36.217
8 78 ms 79 ms 80 ms cr1.attga.ip.att.net [12.122.84.114]
9 79 ms 79 ms 79 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 81 ms 76 ms 81 ms cr2.la2ca.ip.att.net [12.122.28.178]
11 76 ms 75 ms 75 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 225 ms 76 ms 76 ms 12-122-254-234.attens.net [12.122.254.234]
13 77 ms 76 ms 76 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Sitting at about 400ms+ at 9pm EST


Tracing route to 12.129.222.185 over a maximum of 30 hops

1 35 ms 37 ms 24 ms twdp-174-109-144-001.nc.res.rr.com [174.109.144.1]
2 13 ms 15 ms 13 ms a-rtr2-10gig0-2-0-1.2124.nc.rr.com [66.26.46.129]
3 20 ms 37 ms 15 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2]
4 24 ms 23 ms 23 ms 107.14.19.48
5 25 ms 24 ms 30 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
6 29 ms 34 ms * Vlan557.icore1.A56-Atlanta.as6453.net [209.58.44.53]
7 30 ms 31 ms 109 ms 192.205.36.217
8 92 ms * 85 ms cr1.attga.ip.att.net [12.122.84.114]
9 85 ms 87 ms 83 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 105 ms 88 ms 87 ms cr2.la2ca.ip.att.net [12.122.28.178]
11 83 ms 82 ms 82 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 81 ms 82 ms 83 ms 12-122-254-238.attens.net [12.122.254.238]
13 157 ms 221 ms 226 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Join the Conversation

Return to Forum