repeated packet lose
-
Savage
- DW Clan Member
- Posts: 628
- Joined: Thu Mar 26, 2009 2:27 am
- Xfire: savagedogg38
- Location: Dayton, Ohio
- Contact:
I have been having the same issue for a while now and wouldn't consider reporting it if it wasn't so often. I lose all weapons on the last few rounds of the Chicago invasion server. Several levels before the last, my weapons will load slowly one by one after respawning. each time they take longer until some don't load at all. the last two or three levels, I won't get any weapons. I can't see others weapons nor can I see any projectiles that may be heading toward my head. If I can go all rounds without dieing, this never happens. Only when I must spawn do I have this issue. I can fix the problem by reconnected but I lose my score. It may be packet lose but then why doesn't it happen on any other server, even servers with much worse ping don't give me this problem. I am thinking it might be hardware issue on my end. I use cable broadband. Please, if anyone could tell me what I can try to do to resolve this issue, I would greatly appreciate it. Until then, I'll be reconnecting every time I die but I still have a blast killing monsters. Thanks for you time.
-
DW_Cheapshot
- DW Clan Member
- Posts: 377
- Joined: Tue Dec 27, 2005 12:00 am
It does not sound like your hardware is at issue. Packet loss comes in many incarnations, One of the worst
is packet loss on the route to a server. Depending on where you live you may get packet loss to Chicago and not to
New York, as an example. Our server is in Chicago. The route to Chicago has had issues in the past. If you hit the escape key
while in game you will see if it is packet loss and weather others are getting it also. If it is only you the next step is to get a free ping plotter and do a trace route. With this you can for yourself, or if you post it for us to look at we should be able to see where the trouble is.
If it were the server all players should be having the same issue. Although we can not fix a routing issue, this is the isp,s job, we can help isolate the problem just encase it is your issue. IE wireless connections and satellite connections are notorious for causing this issue.
is packet loss on the route to a server. Depending on where you live you may get packet loss to Chicago and not to
New York, as an example. Our server is in Chicago. The route to Chicago has had issues in the past. If you hit the escape key
while in game you will see if it is packet loss and weather others are getting it also. If it is only you the next step is to get a free ping plotter and do a trace route. With this you can for yourself, or if you post it for us to look at we should be able to see where the trouble is.
If it were the server all players should be having the same issue. Although we can not fix a routing issue, this is the isp,s job, we can help isolate the problem just encase it is your issue. IE wireless connections and satellite connections are notorious for causing this issue.
Do not go where the path may lead, go instead where there is no path and leave a trail. Emerson
server 1 has had intermittent serverside lag, mostly on lates when there is a burst of spawners and when they pass the locker their weps HUD bar vanishes then re-appears with weapons. Lots of players have reported these 'big bursts of lag'
-
InflatableHero
- Pro but Noob
- Posts: 133
- Joined: Sun Aug 24, 2008 11:00 pm
I actually had ping spikes the other day and started to get packet loss but I thought it was just me :P
-
DW_Damaged
- DW Clan Member
- Posts: 799
- Joined: Fri Feb 22, 2008 12:00 am
SavageDogg wrote:I have been having the same issue for a while now and wouldn't consider reporting it if it wasn't so often. I lose all weapons on the last few rounds of the Chicago invasion server. Several levels before the last, my weapons will load slowly one by one after respawning. each time they take longer until some don't load at all. the last two or three levels, I won't get any weapons. I can't see others weapons nor can I see any projectiles that may be heading toward my head. If I can go all rounds without dieing, this never happens. Only when I must spawn do I have this issue. I can fix the problem by reconnected but I lose my score. It may be packet lose but then why doesn't it happen on any other server, even servers with much worse ping don't give me this problem. I am thinking it might be hardware issue on my end. I use cable broadband. Please, if anyone could tell me what I can try to do to resolve this issue, I would greatly appreciate it. Until then, I'll be reconnecting every time I die but I still have a blast killing monsters. Thanks for you time.
This use to happen to me and drove me crazy for over a month. I had packet loss but not to the point where I should be losing everything in the game. I rebuilt my machine, replaced all my hardware including MB, memory, CPU and monitor and still had the same problem. I called AT&T and had them run a direct line from my DSL box outside directly to my room so I wouldn’t have to use the DSL filter, I had them switch me to a different circuit and then to a brand new circuit. But I still had the problem. Then one night I was sitting there thinking what the hell could it be and a little light went off in my head and said No Way and it can’t be the POWER SUPPLY. I went out and purchased a new 750w Thermaltake PS and problem solved. I’m not saying this will resolve your problem but whenever someone has the same issues I had the 1dt thing I will always say is check you’re PS.
-
Savage
- DW Clan Member
- Posts: 628
- Joined: Thu Mar 26, 2009 2:27 am
- Xfire: savagedogg38
- Location: Dayton, Ohio
- Contact:
I did a tracert and everything seems fine. I am using a laptop so a new PS is pretty much out. I have heard from others that the ISP modem and router could be the problem. I'll see what I can do about that and get back with ya. Happy fragging!
I have a similar problem and it drives me nuts. I partially blame my absence of UT. However I know it is just a bad connection. I have to share internet with my entire building :pale:
Some days it is good. Other days it is unbearable. I'm just assuming it depends on how many people are using the internet at that specific point in time.
Sorry if this doesn't help, just relating my experience with the evils of packet loss.
Some days it is good. Other days it is unbearable. I'm just assuming it depends on how many people are using the internet at that specific point in time.
Sorry if this doesn't help, just relating my experience with the evils of packet loss.
Adrenaline Master - Inspector lvl 232
Medic - Camisado lvl 255
Weapons Master - Valor lvl 114
Medic - Camisado lvl 255
Weapons Master - Valor lvl 114
-
Savage
- DW Clan Member
- Posts: 628
- Joined: Thu Mar 26, 2009 2:27 am
- Xfire: savagedogg38
- Location: Dayton, Ohio
- Contact:
Okay, tonight it was really bad. I lost more than just weapons and projectiles. Their was times when it was just me all alone in the map with sounds of team mates gunfire all around me. All though interesting, it was very annoying. When I made my concerns known, An_Ant informed me I had lost 44 packets which I have never seen before when I ran the network program within Unreal which I usually run. When I flipped it on it confirmed An_ants comments, I was losing between 10 and 45 packets every second. It has never been that bad before, I might lose 4 or 5 packets once in a while but wow, this time it was bad. So anyway, I ran another tracert and got back way different results than last time. As I matter of fact I can't make heads or tails from it so here it is. By the way, this is the worst it has ever been. I never lag, just lose a few packets, but I lagged really bad today. Here you go, tell me what you think...
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Michael>tracert 208.100.49.220
Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms ;)
2 11 ms 17 ms 8 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 14 ms * * network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 23 ms * * tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 28 ms 29 ms 31 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 * * * Request timed out.
7 * * 40 ms chi-bb1-link.telia.net [213.248.76.97]
8 * 2030 ms * 213.248.104.86
9 * * * Request timed out.
10 * 34 ms 35 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]
Trace complete.
C:\Users\Michael>
P.S. the last tracert looked nothing like this, I promise. I will do another tracert in a half an hour.
P.S.S. I can't seem to past the tracert like in looks in dos but I'm sure you can make it out.
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Michael>tracert 208.100.49.220
Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms ;)
2 11 ms 17 ms 8 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 14 ms * * network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 23 ms * * tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 28 ms 29 ms 31 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 * * * Request timed out.
7 * * 40 ms chi-bb1-link.telia.net [213.248.76.97]
8 * 2030 ms * 213.248.104.86
9 * * * Request timed out.
10 * 34 ms 35 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]
Trace complete.
C:\Users\Michael>
P.S. the last tracert looked nothing like this, I promise. I will do another tracert in a half an hour.
P.S.S. I can't seem to past the tracert like in looks in dos but I'm sure you can make it out.
-
DW_Damaged
- DW Clan Member
- Posts: 799
- Joined: Fri Feb 22, 2008 12:00 am
Your problem appears to be at hop 6, 8 and 9. Wherever you are being routed through 6 is not responding and then as you can see it took 2030 ms at 8 and then again a time out at 9. Something is happening at these points that is causing the problem. If it does not get better call you’re ISP and have them do a tracert to see if they get the same results. They may be able to re-route you through somewhere else.
Hope you get it fixed because I know these things are very annoying.
6 * * * Request timed out.
8 * 2030 ms * 213.248.104.86
9 * * * Request timed out.
Hope you get it fixed because I know these things are very annoying.
6 * * * Request timed out.
8 * 2030 ms * 213.248.104.86
9 * * * Request timed out.
-
Savage
- DW Clan Member
- Posts: 628
- Joined: Thu Mar 26, 2009 2:27 am
- Xfire: savagedogg38
- Location: Dayton, Ohio
- Contact:
Thanks, yesterday was really bad and what you pointed out at 6 and beyong made a lot of sense. Today is much better, I am only losing a few packets every once in a while and having to reconnect less often. So I have added some more tracert information. The first three are to the Chicago Monster Mash server and the last three to three other random unreal server that I usually have little problems with...
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Michael>tracert 208.100.49.220
Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 28 ms 39 ms * cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 10 ms 11 ms 7 ms network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 25 ms * 31 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 31 ms 33 ms 31 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 37 ms 30 ms 30 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 28 ms 30 ms 31 ms chi-bb1-link.telia.net [213.248.76.97]
8 31 ms 30 ms 28 ms steadfast-ic-121572-chi-bb1.c.telia.net [213.248
.104.86]
9 49 ms 33 ms 42 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]
Trace complete.
C:\Users\Michael>tracert 208.100.49.220
Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:
1 3 ms 3 ms 2 ms 192.168.1.1
2 9 ms 10 ms * cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 15 ms 8 ms 10 ms network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 18 ms 20 ms 17 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 30 ms 36 ms 34 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 31 ms 31 ms 34 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 32 ms 32 ms 36 ms chi-bb1-link.telia.net [213.248.76.97]
8 31 ms 32 ms 30 ms steadfast-ic-121572-chi-bb1.c.telia.net [213.248
.104.86]
9 29 ms 28 ms 33 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]
Trace complete.
C:\Users\Michael>tracert 208.100.49.220
Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms 192.168.1.1
2 13 ms 8 ms 109 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 10 ms 9 ms 11 ms network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 17 ms 17 ms 22 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 29 ms 31 ms 29 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 31 ms 34 ms 29 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 32 ms 40 ms 33 ms chi-bb1-link.telia.net [213.248.76.97]
8 31 ms 30 ms 28 ms steadfast-ic-121572-chi-bb1.c.telia.net [213.248
.104.86]
9 39 ms 34 ms 29 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]
Trace complete.
C:\Users\Michael>
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Michael>tracert 8.12.20.203
Tracing route to 8.12.20.203 over a maximum of 30 hops
1 15 ms 17 ms 3 ms 192.168.1.1
2 9 ms 11 ms 8 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 41 ms 17 ms 9 ms network-024-029-165-169.woh.rr.com [24.29.165.16
9]
4 42 ms * 23 ms tge1-0-2.clevoh1-rtr0.mwrtn.rr.com [65.25.137.16
1]
5 25 ms 25 ms 24 ms ae14.mtgmoh1-rtr0.mwrtn.rr.com [65.25.137.150]
6 * 28 ms * xe-10-0-0.bar1.Cincinnati1.Level3.net [4.78.216.
9]
7 41 ms 37 ms 36 ms ae-10-10.ebr2.Chicago1.Level3.net [4.69.136.214]
8 47 ms 37 ms * ge-7-1.ipcolo1.Chicago1.Level3.net [4.68.101.106
]
9 38 ms 45 ms 39 ms 8.12.20.203
Trace complete.
C:\Users\Michael>tracert 166.70.135.171
Tracing route to thalia.magicalspirits.net [166.70.135.171]
over a maximum of 30 hops:
1 5 ms 10 ms 2 ms 192.168.1.1
2 * 11 ms 11 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 8 ms 11 ms 7 ms network-024-029-165-169.woh.rr.com [24.29.165.16
9]
4 8 ms 7 ms 7 ms srp13-0.dytnoh1-rtr1.woh.rr.com [24.29.164.137]
5 18 ms 17 ms 20 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
6 26 ms 31 ms * ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
7 39 ms 39 ms 42 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
8 50 ms 44 ms 57 ms 216.156.72.5.ptr.us.xo.net [216.156.72.5]
9 49 ms 45 ms 47 ms 207.88.13.2.ptr.us.xo.net [207.88.13.2]
10 53 ms * * ge7-0-0d0.rar1.chicago-il.us.xo.net [65.106.1.41
]
11 57 ms * * p6-0-0.rar2.denver-co.us.xo.net [65.106.0.25]
12 62 ms 63 ms * p0-0-0d0.RAR1.Denver-CO.us.xo.net [65.106.1.73]
13 76 ms * * p1-0-0-0.mar1.saltlake-ut.us.xo.net [65.106.6.86
]
14 69 ms 68 ms 68 ms p0-0.chr1.saltlake-ut.us.xo.net [207.88.83.114]
15 77 ms 69 ms 70 ms 67.110.119.234.ptr.us.xo.net [67.110.119.234]
16 64 ms 67 ms 68 ms gi-3-15.dcr2.slc.xmission.net [166.70.5.78]
17 66 ms * 68 ms thalia.magicalspirits.net [166.70.135.171]
Trace complete.
C:\Users\Michael>tracert 209.246.142.152
Tracing route to unknown.Level3.net [209.246.142.152]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 7 ms 7 ms 11 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 10 ms 12 ms 8 ms network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 16 ms * 18 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 29 ms 28 ms 40 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 39 ms 34 ms 34 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 34 ms 42 ms 47 ms ae0-302.cr1.ord1.us.nlayer.net [69.31.111.125]
8 30 ms * 40 ms ae3.cr2.ord1.us.nlayer.net [69.31.111.154]
9 95 ms * 53 ms xe-0-3-0.cr1.dfw1.us.nlayer.net [69.22.142.1]
10 60 ms * 111 ms po3.ar1.dfw1.us.nlayer.net [69.31.63.126]
11 55 ms * 56 ms as20473.tge5-2.ar1.dfw1.us.nlayer.net [69.31.63.
38]
12 56 ms 52 ms * unknown.Level3.net [209.246.142.152]
13 250 ms 63 ms 61 ms unknown.Level3.net [209.246.142.152]
Trace complete.
C:\Users\Michael>
P.S. I am guessing they must have resolved the problem at 6,7, and 8, over night or maybe it deals with a lot of traffic during those hours, it does seem to get worse for me at night now that I think about it so I'll do more tracerts throughout the day and make a log of it. don't worry though, I won't post that. It would be a mess but I will tell you what I have found.
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Michael>tracert 208.100.49.220
Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 28 ms 39 ms * cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 10 ms 11 ms 7 ms network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 25 ms * 31 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 31 ms 33 ms 31 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 37 ms 30 ms 30 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 28 ms 30 ms 31 ms chi-bb1-link.telia.net [213.248.76.97]
8 31 ms 30 ms 28 ms steadfast-ic-121572-chi-bb1.c.telia.net [213.248
.104.86]
9 49 ms 33 ms 42 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]
Trace complete.
C:\Users\Michael>tracert 208.100.49.220
Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:
1 3 ms 3 ms 2 ms 192.168.1.1
2 9 ms 10 ms * cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 15 ms 8 ms 10 ms network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 18 ms 20 ms 17 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 30 ms 36 ms 34 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 31 ms 31 ms 34 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 32 ms 32 ms 36 ms chi-bb1-link.telia.net [213.248.76.97]
8 31 ms 32 ms 30 ms steadfast-ic-121572-chi-bb1.c.telia.net [213.248
.104.86]
9 29 ms 28 ms 33 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]
Trace complete.
C:\Users\Michael>tracert 208.100.49.220
Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms 192.168.1.1
2 13 ms 8 ms 109 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 10 ms 9 ms 11 ms network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 17 ms 17 ms 22 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 29 ms 31 ms 29 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 31 ms 34 ms 29 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 32 ms 40 ms 33 ms chi-bb1-link.telia.net [213.248.76.97]
8 31 ms 30 ms 28 ms steadfast-ic-121572-chi-bb1.c.telia.net [213.248
.104.86]
9 39 ms 34 ms 29 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]
Trace complete.
C:\Users\Michael>
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Michael>tracert 8.12.20.203
Tracing route to 8.12.20.203 over a maximum of 30 hops
1 15 ms 17 ms 3 ms 192.168.1.1
2 9 ms 11 ms 8 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 41 ms 17 ms 9 ms network-024-029-165-169.woh.rr.com [24.29.165.16
9]
4 42 ms * 23 ms tge1-0-2.clevoh1-rtr0.mwrtn.rr.com [65.25.137.16
1]
5 25 ms 25 ms 24 ms ae14.mtgmoh1-rtr0.mwrtn.rr.com [65.25.137.150]
6 * 28 ms * xe-10-0-0.bar1.Cincinnati1.Level3.net [4.78.216.
9]
7 41 ms 37 ms 36 ms ae-10-10.ebr2.Chicago1.Level3.net [4.69.136.214]
8 47 ms 37 ms * ge-7-1.ipcolo1.Chicago1.Level3.net [4.68.101.106
]
9 38 ms 45 ms 39 ms 8.12.20.203
Trace complete.
C:\Users\Michael>tracert 166.70.135.171
Tracing route to thalia.magicalspirits.net [166.70.135.171]
over a maximum of 30 hops:
1 5 ms 10 ms 2 ms 192.168.1.1
2 * 11 ms 11 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 8 ms 11 ms 7 ms network-024-029-165-169.woh.rr.com [24.29.165.16
9]
4 8 ms 7 ms 7 ms srp13-0.dytnoh1-rtr1.woh.rr.com [24.29.164.137]
5 18 ms 17 ms 20 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
6 26 ms 31 ms * ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
7 39 ms 39 ms 42 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
8 50 ms 44 ms 57 ms 216.156.72.5.ptr.us.xo.net [216.156.72.5]
9 49 ms 45 ms 47 ms 207.88.13.2.ptr.us.xo.net [207.88.13.2]
10 53 ms * * ge7-0-0d0.rar1.chicago-il.us.xo.net [65.106.1.41
]
11 57 ms * * p6-0-0.rar2.denver-co.us.xo.net [65.106.0.25]
12 62 ms 63 ms * p0-0-0d0.RAR1.Denver-CO.us.xo.net [65.106.1.73]
13 76 ms * * p1-0-0-0.mar1.saltlake-ut.us.xo.net [65.106.6.86
]
14 69 ms 68 ms 68 ms p0-0.chr1.saltlake-ut.us.xo.net [207.88.83.114]
15 77 ms 69 ms 70 ms 67.110.119.234.ptr.us.xo.net [67.110.119.234]
16 64 ms 67 ms 68 ms gi-3-15.dcr2.slc.xmission.net [166.70.5.78]
17 66 ms * 68 ms thalia.magicalspirits.net [166.70.135.171]
Trace complete.
C:\Users\Michael>tracert 209.246.142.152
Tracing route to unknown.Level3.net [209.246.142.152]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 7 ms 7 ms 11 ms cpe-71-64-128-1.woh.res.rr.com [71.64.128.1]
3 10 ms 12 ms 8 ms network-024-029-165-165.woh.rr.com [24.29.165.16
5]
4 16 ms * 18 ms tge1-0-2.clboh1-rtr0.mwrtn.rr.com [65.25.137.177
]
5 29 ms 28 ms 40 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 39 ms 34 ms 34 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 34 ms 42 ms 47 ms ae0-302.cr1.ord1.us.nlayer.net [69.31.111.125]
8 30 ms * 40 ms ae3.cr2.ord1.us.nlayer.net [69.31.111.154]
9 95 ms * 53 ms xe-0-3-0.cr1.dfw1.us.nlayer.net [69.22.142.1]
10 60 ms * 111 ms po3.ar1.dfw1.us.nlayer.net [69.31.63.126]
11 55 ms * 56 ms as20473.tge5-2.ar1.dfw1.us.nlayer.net [69.31.63.
38]
12 56 ms 52 ms * unknown.Level3.net [209.246.142.152]
13 250 ms 63 ms 61 ms unknown.Level3.net [209.246.142.152]
Trace complete.
C:\Users\Michael>
P.S. I am guessing they must have resolved the problem at 6,7, and 8, over night or maybe it deals with a lot of traffic during those hours, it does seem to get worse for me at night now that I think about it so I'll do more tracerts throughout the day and make a log of it. don't worry though, I won't post that. It would be a mess but I will tell you what I have found.