Time Warner Bright House Insight Latency

Technical Support
Prev 1 3 4 5 Next
So can we all agree its not just the above named ISPs? Not really a fan of being broadcasted that TWC/Insight/Bright House latency being blamed when from what I can see its not only those companies having issues and clearly not from their end that the issue has arose.
i live in tampa area fl

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Rcomputer>tracert.exe

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
[-R] [-S srcaddr] [-4] [-6] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Wait timeout milliseconds for each reply.
-R Trace round-trip path (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Force using IPv4.
-6 Force using IPv6.

C:\Users\Rcomputer>tracert battle.net

Tracing route to battle.net [12.129.242.30]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 21 ms 8 ms 7 ms 10.113.0.1
3 8 ms 9 ms 8 ms 72-31-3-21.net.bhntampa.com [72.31.3.21]
4 31 ms 10 ms 11 ms ten0-2-0-4.tamp27-car1.bhn.net [72.31.209.120]
5 58 ms 12 ms 22 ms ten0-1-0-6.tamp20-car1.bhn.net [72.31.208.34]
6 19 ms 23 ms 15 ms hun0-0-0-0-tamp20-cbr1.bhn.net [72.31.117.156]
7 36 ms 32 ms 108 ms ae-11-11.cr0.dfw10.tbone.rr.com [66.109.10.12]
8 40 ms 39 ms 37 ms 107.14.19.156
9 74 ms 34 ms 37 ms 107.14.17.234
10 35 ms 39 ms 40 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.
97]
11 39 ms 37 ms 35 ms if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5
]
12 33 ms 36 ms 34 ms 192.205.36.205
13 71 ms 83 ms 72 ms cr2.dlstx.ip.att.net [12.122.212.14]
14 71 ms 71 ms 75 ms cr2.la2ca.ip.att.net [12.122.28.178]
15 77 ms 69 ms 345 ms gar29.la2ca.ip.att.net [12.122.129.241]
16 73 ms 205 ms 603 ms 12-122-254-238.attens.net [12.122.254.238]
17 228 ms 174 ms 69 ms 206.16.68.46
18 * * * Request timed out.
19 * * * Request timed out.
20 * *
I also use brighthouse
sorry i use this guy not my panda sorry for the mix up in first post.
Really hoping that was sarcasm because *day after being down for almost a week is not a good time frame at all.


It is certainly frustrating, but do consider the big picture. Working on the assumption this is congestion between network providers it is more complicated then just replacing a server or bad memory. The involved provider(s) need to be contacted and notified of the issue which hopefully they are already aware of and working towards a solution. Those providers may need to create new contracts or agreements to expand their capacity between each other and then physical connections need to be run and tested. That could be as simple as running a cable between switches or routers located in the same room or as complicated as having new connections run miles between the providers. In some cases this process could take months.

This is a fairly dated article but many of the concepts are still applicable if you are interested in further understanding the complexity behind the scenes of how internet traffic moves.

http://computer.howstuffworks.com/internet/basics/internet-infrastructure.htm

Hope your connection clears up soon.
So can we all agree its not just the above named ISPs? Not really a fan of being broadcasted that TWC/Insight/Bright House latency being blamed when from what I can see its not only those companies having issues and clearly not from their end that the issue has arose.

You're right, this issue doesn't exist on those ISP's network, so it won't help to contact these ISPs. We've isolated the issue to the South and Southeast region. We've escalated the issue on our players' behalf to the parties involved, and a solution is underway. We also don't see any other latency issues related to this particular incident.
________________________________________________
Monday - Friday, 8 am - 5 pm PST
Given this incident is there a way to update subscriptions for time lost. I just updated my account with 30 more days just the other day and I am having such a hard time getting in game and not disconnecting.
Given this incident is there a way to update subscriptions for time lost. I just updated my account with 30 more days just the other day and I am having such a hard time getting in game and not disconnecting.


Ollopa, I don't want to get your hopes up but you may want to call them and ask if they could put your account on hold for a few days until things are more solid. I believe they have done this for people during disasters but not sure about situations like this. Couldn't hurt to try I suppose.
As you can see from all of the tracerts, it always breaks at the AT&T servers.

I've been having this issues since the beginning of February, like many other brazilian players, as seen here: http://us.battle.net/wow/pt/forum/topic/8568986971

Unfortunately, most of our connections here in Brazil go through that AT&T route. Our Blizzard reps said they've contacted AT&T about the issue too.

I hope this fix Velnrak talked about also fixes things for us down here.
Ollopa, I don't want to get your hopes up but you may want to call them and ask if they could put your account on hold for a few days until things are more solid. I believe they have done this for people during disasters but not sure about situations like this. Couldn't hurt to try I suppose.


Raising a ticket at :

https://us.battle.net/support/en/ticket/submit

Would be the best way of getting the ball rolling on that. Can reference this thread about it. If it's necessary to call through and their call center is open phone numbers are provided. Live Chat option as well.

A billing rep can make the call on having to refund or not.
When I raid on my alts on other servers (hosted on LA datacenter), I have 70-80ms latency. However, on Mal'ganis (NY datacenter), I have been raiding with over 100ms latency for past 3 weeks and it shoots up to 700ms+ every once in a while for a few minutes, which needless to say often results in my death.

Here's what I typically have: http://i.imgur.com/m0i0PJj.jpg
Here's the edge case that I experience a few times every night: http://i.imgur.com/Q1msHg2.jpg

1. Trace route:
Tracing route to 63.240.104.93 over a maximum of 30 hops

1 19 ms 31 ms 19 ms cpe-76-92-160-1.kc.res.rr.com [76.92.160.1]
2 11 ms 11 ms 11 ms tge7-2.ovpmks48-cer2.kc.rr.com [65.28.16.62]
3 12 ms 14 ms 14 ms tge0-8-0-1.ksczksmp-ccr1.kc.rr.com [98.156.42.134]
4 65 ms 70 ms 54 ms ae30.hstntxl3-cr01.kc.rr.com [98.156.42.2]
5 57 ms 54 ms 54 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
6 37 ms 36 ms 36 ms 107.14.17.141
7 37 ms 36 ms 36 ms ge5-0-2d0.cir1.dallas2-tx.us.xo.net [65.47.204.29]
8 41 ms 42 ms 38 ms 192.205.36.101
9 106 ms 90 ms 89 ms cr1.dlstx.ip.att.net [12.123.18.74]
10 87 ms 90 ms 89 ms cr2.nsvtn.ip.att.net [12.122.1.242]
11 89 ms 90 ms 89 ms cr1.cl2oh.ip.att.net [12.122.28.74]
12 90 ms 86 ms 90 ms cr2.cl2oh.ip.att.net [12.122.2.126]
13 92 ms 90 ms 90 ms cr2.phlpa.ip.att.net [12.122.2.210]
14 85 ms 85 ms 84 ms gar1.pitpa.ip.att.net [12.122.107.85]
15 168 ms 102 ms 112 ms 12.122.251.2
16 91 ms 91 ms 90 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
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.


2. Pathping:
Tracing route to 63.240.104.93 over a maximum of 30 hops

0 Scope-PC.kc.rr.com [76.92.189.212]
1 cpe-76-92-160-1.kc.res.rr.com [76.92.160.1]
2 tge7-2.ovpmks48-cer2.kc.rr.com [65.28.16.62]
3 tge0-8-0-1.ksczksmp-ccr1.kc.rr.com [98.156.42.134]
4 ae30.hstntxl3-cr01.kc.rr.com [98.156.42.2]
5 ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
6 107.14.17.141
7 ge5-0-2d0.cir1.dallas2-tx.us.xo.net [65.47.204.29]
8 192.205.36.101
9 cr1.dlstx.ip.att.net [12.123.18.74]
10 cr2.nsvtn.ip.att.net [12.122.1.242]
11 cr1.cl2oh.ip.att.net [12.122.28.74]
12 cr2.cl2oh.ip.att.net [12.122.2.126]
13 cr2.phlpa.ip.att.net [12.122.2.210]
14 gar1.pitpa.ip.att.net [12.122.107.85]
15 12-122-254-242.attens.net [12.122.254.242]
16 mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
17 * * *
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Scope-PC.kc.rr.com [76.92.189.212]
0/ 100 = 0% |
1 14ms 0/ 100 = 0% 0/ 100 = 0% cpe-76-92-160-1.kc.res.rr.com [76.92.160.1]
0/ 100 = 0% |
2 16ms 1/ 100 = 1% 1/ 100 = 1% tge7-2.ovpmks48-cer2.kc.rr.com [65.28.16.62]
0/ 100 = 0% |
3 19ms 0/ 100 = 0% 0/ 100 = 0% tge0-8-0-1.ksczksmp-ccr1.kc.rr.com [98.156.42.134]
0/ 100 = 0% |
4 55ms 0/ 100 = 0% 0/ 100 = 0% ae30.hstntxl3-cr01.kc.rr.com [98.156.42.2]
0/ 100 = 0% |
5 58ms 0/ 100 = 0% 0/ 100 = 0% ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
0/ 100 = 0% |
6 48ms 0/ 100 = 0% 0/ 100 = 0% 107.14.17.141
0/ 100 = 0% |
7 48ms 1/ 100 = 1% 1/ 100 = 1% ge5-0-2d0.cir1.dallas2-tx.us.xo.net [65.47.204.29]
0/ 100 = 0% |
8 44ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.101
100/ 100 =100% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.123.18.74]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.nsvtn.ip.att.net [12.122.1.242]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.cl2oh.ip.att.net [12.122.28.74]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.cl2oh.ip.att.net [12.122.2.126]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr2.phlpa.ip.att.net [12.122.2.210]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% gar1.pitpa.ip.att.net [12.122.107.85]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-242.attens.net [12.122.254.242]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]

Trace complete.


3. Location: Kansas City, KS

4. Time Warner internet with wired connection directly to the modem. Single computer with only mumble and WoW permitted internet access during raids.

5. Modem: Ambit
Model #: U10C018
Issue seems to be fixed for me. My framerate is back to normal. :-)
Issue seems to be fixed for me. My framerate is back to normal. :-)
This thread is about latency, not framerate and it's definitely not fixed yet. Still getting 700ms+ latency spikes for a few mins every couple hours.
Just spiked in a bg, everyone was running in place, this sh*t is TERRIBLE!!!


Tracing route to 12.129.222.185 over a maximum of 30 hops

1 39 ms 76 ms 46 ms twdp-174-109-144-001.nc.res.rr.com [174.109.144.1]
2 13 ms 15 ms 11 ms a-rtr2-10gig0-2-0-1.2124.nc.rr.com [66.26.46.129]
3 18 ms 17 ms 21 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2]
4 33 ms 29 ms 27 ms 107.14.19.48
5 23 ms 22 ms 22 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
6 29 ms 35 ms * Vlan510.icore1.A56-Atlanta.as6453.net [209.58.44.13]
7 24 ms 24 ms 24 ms 192.205.36.217
8 81 ms 77 ms 78 ms cr1.attga.ip.att.net [12.122.84.114]
9 82 ms 82 ms 143 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 82 ms 79 ms 79 ms cr2.la2ca.ip.att.net [12.122.28.178]
11 79 ms 78 ms 76 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 77 ms 79 ms 79 ms 12-122-254-238.attens.net [12.122.254.238]
13 91 ms 78 ms 79 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 another trace, only spiking in BGS atm, Gilneas was UNPLAYABLE!!


Tracing route to 12.129.222.185 over a maximum of 30 hops

1 35 ms 27 ms 29 ms twdp-174-109-144-001.nc.res.rr.com [174.109.144.1]
2 13 ms 13 ms 12 ms a-rtr2-10gig0-2-0-1.2124.nc.rr.com [66.26.46.129]
3 19 ms 20 ms 34 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2]
4 32 ms 31 ms 23 ms 107.14.19.48
5 22 ms 24 ms 25 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
6 24 ms * * Vlan510.icore1.A56-Atlanta.as6453.net [209.58.44.13]
7 25 ms 28 ms 24 ms 192.205.36.217
8 77 ms 78 ms 79 ms cr1.attga.ip.att.net [12.122.84.114]
9 76 ms 79 ms 79 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 81 ms 99 ms 81 ms cr2.la2ca.ip.att.net [12.122.28.178]
11 78 ms 75 ms 76 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 76 ms 81 ms 78 ms 12-122-254-234.attens.net [12.122.254.234]
13 77 ms 79 ms 79 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.
04/27/2013 02:58 PMPosted by Skhope
This thread is about latency, not framerate and it's definitely not fixed yet.


Whether it's about latency or not, I have been experiencing an issue for the last week that was not of my making. My framerate was extremely low and I would see latency spikes. The game was virtually unplayable so something was fixed. My ISP is AT&T Uverse and I am in Florida if that helps.
I think this is happening with Comcast as well.......I'm in the Sarasota area.......
Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:

1 38 ms 27 ms 14 ms cpe-75-82-192-1.socal.res.rr.com [75.82.192.1]
2 10 ms 9 ms * tge7-5.mnrvca71-cer02.socal.rr.com [76.166.6.53]
3 15 ms 16 ms * tge0-10-0-6.lamrcadq-ccr02.socal.rr.com [72.129.10.104]
4 19 ms 15 ms 16 ms agg28.tustcaft-ccr01.socal.rr.com [72.129.9.2]
5 16 ms 15 ms 31 ms ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
6 19 ms 16 ms 16 ms 107.14.19.67
7 15 ms 15 ms 19 ms ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
8 18 ms 17 ms 15 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
9 17 ms 34 ms 15 ms 66.110.59.42
10 37 ms 38 ms 40 ms cr1.la2ca.ip.att.net [12.122.82.246]
11 * 53 ms 32 ms cr2.phmaz.ip.att.net [12.122.31.190]
12 * 28 ms 140 ms 12.122.108.105
13 50 ms 41 ms 42 ms 12-122-254-218.attens.net [12.122.254.218]
14 435 ms 29 ms 27 ms mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]
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 mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 EVE [192.168.0.4]
1 cpe-75-82-192-1.socal.res.rr.com [75.82.192.1]
2 tge7-5.mnrvca71-cer02.socal.rr.com [76.166.6.53]
3 tge0-10-0-6.lamrcadq-ccr02.socal.rr.com [72.129.10.104]
4 agg28.tustcaft-ccr01.socal.rr.com [72.129.9.2]
5 ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
6 107.14.19.67
7 ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
8 if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
9 66.110.59.42
10 cr1.la2ca.ip.att.net [12.122.82.246]
11 cr2.phmaz.ip.att.net [12.122.31.190]
12 12.122.108.105
13 12-122-254-218.attens.net [12.122.254.218]
14 mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 EVE [192.168.0.4]
1/ 100 = 1% |
1 41ms 2/ 100 = 2% 1/ 100 = 1% cpe-75-82-192-1.socal.res.rr.com [75.82.192.1]
0/ 100 = 0% |
2 39ms 1/ 100 = 1% 0/ 100 = 0% tge7-5.mnrvca71-cer02.socal.rr.com [76.166.6.53]
0/ 100 = 0% |
3 42ms 1/ 100 = 1% 0/ 100 = 0% tge0-10-0-6.lamrcadq-ccr02.socal.rr.com [72.129.10.104]
0/ 100 = 0% |
4 40ms 1/ 100 = 1% 0/ 100 = 0% agg28.tustcaft-ccr01.socal.rr.com [72.129.9.2]
0/ 100 = 0% |
5 41ms 2/ 100 = 2% 1/ 100 = 1% ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
0/ 100 = 0% |
6 28ms 1/ 100 = 1% 0/ 100 = 0% 107.14.19.67
0/ 100 = 0% |
7 21ms 1/ 100 = 1% 0/ 100 = 0% ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
1/ 100 = 1% |
8 24ms 2/ 100 = 2% 0/ 100 = 0% if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
0/ 100 = 0% |
9 29ms 2/ 100 = 2% 0/ 100 = 0% 66.110.59.42
98/ 100 = 98% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.82.246]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.phmaz.ip.att.net [12.122.31.190]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% 12.122.108.105
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-218.attens.net [12.122.254.218]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]

Trace complete.

Location: Monrovia, CA
99% wired, but issues remain the same on wireless
Modem: Motorola, Surfboard SBG6580
Aevinay. Your issue appears to be different from the other people suffering latency in this thread. You can see that from your first hops in your pathping you are dropping 1-2% of the packets right out the gate. I've found WoW to become unplayable around .5-1% loss.

You might consider firing up a separate thread and asking for one of the support folks to provide additional recommendations. I'd personally start with checking all my physical connections to make sure they are secure. Additionally it wouldn't hurt to give your internet provider a ring and ask them to check the signal on your modem. Explain to them that you are seeing packet loss starting at your cable modem.

Best of luck.
I have been having connection issues with Brighthouse of Central Florida for some time. I live in South Daytona, Florida. I had tried to work with BH however I kept on them so much they actually dropped me as a customer. The service is now in my gf's name and with BH and the issues persist. I am attaching my most recent Pathping and traceroutes to help with this. Hopefully resolution of this occurs soon. As well the issue is the same wired or wireless connection, however these tests where performed with a wired connection.

PathPing


Tracing route to Unknown.cerfnet.net [206.16.118.244]
over a maximum of 30 hops:
0 Chris-PC.cfl.rr.com [192.168.0.4]
1 192.168.0.1
2 10.109.16.1
3 72-31-193-236.net.bhntampa.com [72.31.193.236]
4 ten0-15-0-4.orld11-car1.bhn.net [97.69.193.76]
5 ten0-1-0-0.orld71-car1.bhn.net [97.69.193.136]
6 72-31-193-133.net.bhntampa.com [72.31.193.133]
7 ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
8 107.14.19.78
9 107.14.19.13
10 216.156.108.65.ptr.us.xo.net [216.156.108.65]
11 67.111.23.90.ptr.us.xo.net [67.111.23.90]
12 cr2.attga.ip.att.net [12.122.84.150]
13 cr1.nwrla.ip.att.net [12.122.18.2]
14 cr1.dlstx.ip.att.net [12.122.1.209]
15 cr1.phmaz.ip.att.net [12.122.28.182]
16 cr2.phmaz.ip.att.net [12.122.1.17]
17 12.122.108.105
18 mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
19 * mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
20 * * *
Computing statistics for 475 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Chris-PC.cfl.rr.com [192.168.0.4]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.109.16.1
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 72-31-193-236.net.bhntampa.com [72.31.193.236]
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% ten0-15-0-4.orld11-car1.bhn.net [97.69.193.76]
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% ten0-1-0-0.orld71-car1.bhn.net [97.69.193.136]
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% 72-31-193-133.net.bhntampa.com [72.31.193.133]
0/ 100 = 0% |
7 30ms 0/ 100 = 0% 0/ 100 = 0% ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
0/ 100 = 0% |
8 29ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.78
0/ 100 = 0% |
9 31ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.13
0/ 100 = 0% |
10 37ms 0/ 100 = 0% 0/ 100 = 0% 216.156.108.65.ptr.us.xo.net [216.156.108.65]
0/ 100 = 0% |
11 35ms 0/ 100 = 0% 0/ 100 = 0% 67.111.23.90.ptr.us.xo.net [67.111.23.90]
100/ 100 =100% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.attga.ip.att.net [12.122.84.150]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr1.nwrla.ip.att.net [12.122.18.2]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.1.209]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr1.phmaz.ip.att.net [12.122.28.182]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% cr2.phmaz.ip.att.net [12.122.1.17]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.108.105
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
0/ 100 = 0% |
19 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]

Trace complete.


Tracert.txt
Tracing route to Unknown.cerfnet.net [206.16.118.244]
over a maximum of 30 hops:

1 2 ms 2 ms 5 ms 192.168.0.1
2 9 ms 11 ms 12 ms 10.109.16.1
3 11 ms 10 ms 11 ms 72-31-193-236.net.bhntampa.com [72.31.193.236]
4 15 ms 15 ms 14 ms ten0-15-0-4.orld11-car1.bhn.net [97.69.193.76]
5 20 ms 22 ms 24 ms ten0-1-0-0.orld71-car1.bhn.net [97.69.193.136]
6 15 ms 20 ms 22 ms 72-31-193-133.net.bhntampa.com [72.31.193.133]
7 26 ms 28 ms 28 ms ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
8 26 ms 27 ms 30 ms 107.14.19.78
9 60 ms 25 ms 24 ms 107.14.19.13
10 29 ms 26 ms 27 ms 216.156.108.65.ptr.us.xo.net [216.156.108.65]
11 50 ms 29 ms 24 ms 67.111.23.90.ptr.us.xo.net [67.111.23.90]
12 86 ms 82 ms 80 ms cr1.attga.ip.att.net [12.122.84.114]
13 79 ms 86 ms 82 ms cr1.nwrla.ip.att.net [12.122.18.2]
14 78 ms 79 ms 80 ms cr1.hs1tx.ip.att.net [12.122.1.141]
15 88 ms 81 ms 85 ms cr1.phmaz.ip.att.net [12.122.28.182]
16 82 ms 81 ms 79 ms cr2.phmaz.ip.att.net [12.122.1.17]
17 83 ms 78 ms 77 ms 12-122-254-218.attens.net [12.122.254.218]
18 76 ms 78 ms 77 ms mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
19 * 84 ms 79 ms mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
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