Lorcan8
join:2001-03-20
Rosemount, MN
1 edit | reply to oogla
Re: [HSI] Intermittent routing problem in Rochester MN
Sometimes, I go to bed later and happen to be doing something past midnight (no later than 1am, though) and I have actually noticed the exact same thing. I live in Rosemount, and I am unsure as to if it constantly happens at that time, but I have noticed this happening before midnight at times (10:30pm, 11pm area), but it is almost always after midnight. In one example, I was playing TF2 on my favorite server, because a lot of people from my area play there, and its out of Chicago. Normally I get an extremely low ping (12ms-25ms) and it pretty much goes to chicago and back. However, it now is always 50-70ms and I do, at times, magically time out.
Examples of this is that I'd be fine, then the game would freeze, and I would time out to the server. Then maybe 10 or 15 minutes later, I'll be able to get back on....and after an undetermined amount of time, I'd time out again. During those times, I could use IRC, connecting to undernet, but it won't reach all of their servers or a bulk of the websites out there. I have actually noticed the same servers you mention in your post in some of my traceroutes. The traceroute right now looks like this:
Tracing route to 69.90.119.158 over a maximum of 30 hops
1 8 ms 6 ms 7 ms 10.151.208.1
2 8 ms 9 ms 9 ms 96.34.25.20
3 10 ms 7 ms 7 ms dtr01owtnmn-gbe-6-1.roch.mn.charter.com [96.34.16.108]
4 8 ms 9 ms 8 ms crr01owtnmn-gbe-2-0-0.roch.mn.charter.com [96.34.25.148]
5 9 ms 8 ms 7 ms edr01owtnmn-gbe-1-0-0.roch.mn.charter.com [96.34.25.11]
6 30 ms 18 ms 20 ms kcm-edge-13.inet.qwest.net [72.166.94.49]
7 32 ms 33 ms 31 ms dap-brdr-03.inet.qwest.net [67.14.2.89]
8 33 ms 54 ms 32 ms xe-8-2-0.edge2.dallas3.level3.net [4.68.63.53]
9 35 ms 34 ms 35 ms vlan69.csw1.Dallas1.Level3.net [4.68.19.62]
10 36 ms 36 ms 33 ms ae-62-62.ebr2.Dallas1.Level3.net [4.69.136.137]
11 50 ms 39 ms 49 ms ae-2.ebr1.Denver1.Level3.net [4.69.132.105]
12 48 ms 38 ms 50 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
13 51 ms 51 ms 54 ms ae-3.ebr1.Chicago2.Level3.net [4.69.132.62]
14 58 ms 53 ms 57 ms ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
15 53 ms 53 ms 52 ms ae-14-53.car4.Chicago1.Level3.net [4.68.101.72]
16 54 ms 54 ms 55 ms PEER-1-NETW.car4.Chicago1.Level3.net [4.71.102.98]
17 53 ms 54 ms 54 ms 69.90.119.158
It definitely never took the long way to chicago before, and when it starts to time out, I believe it is hops 4 and 5 that it does the same thing as the OP. When it happened after reading this post, I did a traceroute to the same location as the OP and had the same results. I, too, couldn't get to dslreports during this time. In fact, when I would refresh the list of favorites in Steam (for TF2), some would time out and some of them were still responding. The ones that timed out, I believe, were all located in Chicago. I could be wrong, but I believe they all were. It hasn't really inconvenienced me TOO much, but it is pretty annoying. I haven't noticed it the last 2 days, but I thought I'd just throw in my 2 cents anyways. |
