Level3 issues? Post some info here

1) We UK users posting the US traceroutes are playing on the US servers.
2) Last night I was at 32k and not surprisingly it took 29 seconds for actions to register, the insane latency readings are not false (for me). I can't tell you that the majority of the 29 seconds are spent at Level3, but when playing on a server or game that hasn't routed through Level3 there are no problems.
3) Traceroutes do provide some information, they need to tell us what info they need.
4) Most PS2 users didn't blame Level3 at first, they do now as SOE have acknowledged there's a problem.

To wuffar and the person doubting any latency above 10k, I'll record a video later when the issues kick in and show you =).

What I think is rather strange is that all PS2 players are supposed to get in contact with their ISPs to solve this issue. Since it started for almost everyone at the same time, it seems that the issue is clearly with Level3. They maybe changed something which causes these high latencies. And knowing how incompetent the support of some ISPs can be (standardised replies, guys in support who have no clue about an issue like this, several days waiting time for each single reply from support which happens to be just another standardised reply which does not deal with the issue again etc), I think I won't be able to play this game at prime time anymore.

Something changed on Level3's side somewhere around 10 days ago and all of a sudden a very large portion of players can't play the game anymore. So to fix this, there should be an easier solution than "everyone, contact your ISPs and try to resolve the issue from their side". This won't work I'm afraid.

yeah lets contact out ISP and tell them out video game isnt working. see how much they care

as partybooper stated, this is a universal problem with one common denominator

Now you're just derailing everything about this thread. I stated SOE has used Level3 for a very long time. (They've had problems for as long as I can remember being an SOE customer)

They aren't a major backbone, they're just a hub where it gets routed out to another hub. Being a backbone literally means you control a major pipeline throughout a state or network of states with fiber-optic or other internet means. All Level3 does is literally move one connection to another (which they also pay for their own internet provider). So, even doing what they state they do, they fail at it.

I don't have any problems, game is working just fine here.. only did it for lol;s like i said, but cmoon level 3 sucks if it hops from Finland-Stockholm 23ms to Stockholm-Stockholm 204ms level3 network.. there really is something wrong with that network if i get WAY better ms over the sea than they get on same city, it sure ain't a problem on Sweden network since we all know they have pretty darn good ones!

My 200ms is pretty much what it should be to USA from here, but never the less they should do some work to the network, at least near to my location.. so 200ms over the big sea is OK, 200ms on same town when changing network is kinda meh!

This evening I started having problems. 15000+ ms latency and poor/bad connection quality.

lp.soe.com [64.37.171.24]

1 1 ms 1 ms 1 ms 192.168.1.1
2 22 ms 22 ms 23 ms 85.110.0.1.static.ttnet.com.tr [85.110.0.1]
3 24 ms 23 ms 23 ms 81.212.77.85.static.turktelekom.com.tr [81.212.77.85]
4 * * * ˜stek zaman aŸmna u§rad.
5 * * * ˜stek zaman aŸmna u§rad.
6 * * * ˜stek zaman aŸmna u§rad.
7 120 ms 119 ms * 212.73.241.173
8 123 ms 124 ms 123 ms ae-0-11.bar1.Milan1.Level3.net [4.69.142.189]
9 266 ms 269 ms 267 ms ae-8-8.ebr3.Paris1.Level3.net [4.69.142.186]
10 233 ms 233 ms 233 ms ae-83-83.csw3.Paris1.Level3.net [4.69.161.118]
11 234 ms 234 ms 233 ms ae-82-82.ebr2.Paris1.Level3.net [4.69.161.101]
12 233 ms 233 ms 233 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.58]
13 230 ms 231 ms 233 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
14 231 ms 231 ms 231 ms ae-81-81.ebr1.Washington1.Level3.net [4.69.134.137]
15 * * * ˜stek zaman aŸmna u§rad.
16 231 ms 229 ms 230 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
17 237 ms 234 ms 233 ms ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]
18 230 ms 229 ms 232 ms ae-72-72.ebr2.Dallas1.Level3.net [4.69.151.142]
19 232 ms 234 ms 229 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
20 258 ms 256 ms 230 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
21 294 ms 229 ms 229 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
22 230 ms 231 ms 230 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
23 231 ms 229 ms 229 ms lp.soe.com [64.37.171.24]


Looks like hop 4-5-6-15 did totally time out. My Internet speed is generally slow atm.

Again... it's because the NSA is data collecting through Level3

High 80 ms ping average, though I am in Germany close to capital city (ping to amsterdam = 20-30 normally).

Also I checked the route (trace) and it gave me 100% packet loss at the point where the route reaches Level 3...

It's unplayable again on Ceres here from Germany.

And SOE will not try to contact Level3 themselves about this big issue? We really are left with "Ask your ISPs about it"? If it stays like this, all I can do is stop playing. Cause this is unplayable.

Just wanted to post here to say a couple things. First this is a great tool for doing ping tests / trace routes. http://winmtr.net/download-winmtr/ I've been using that tool for years. It's only available for windows but i'm pretty sure if your playing planetside 2 you have a copy of windows. Not only that but it is a tiny and lightweight program. Obviously with any ping testing or any network testing don't have anything downloading as it could give inaccurate results.

For the past month or so I've been noticing some weird behavior with my internet. For almost an entire week I was banging my head thinking it was a problem on my end. Turns out it was a problem on Cogents end (another tier 3 service provider I was testing this against battlefield servers and CS:GO servers). I then changed to a server that routed through level3 while it would have an occasional packet loss or small latency spikes (like you could watch your ping stable at 30ms for 20secs or more than one or two seconds it would spike to a ping of 60 and jump back down).

I then found out something quite interesting because I usually play in the afternoons one morning I decided to do some testing. It was about 10AM my local time (I live on the US East Coast btw). I ran a traceroute test for a solid 30 minutes not a single spike in ping or even a single packet loss. I hopped onto the server and could definitely feel the difference. So I believe this is a prime time issue. Not to mention when you route 3,000 more miles on a different server and it has better ping / stability you realize it's a overload issue. Not only that but I'm starting to see more and more things slow down during prime time.

Youtube also takes a huge hit. Granted we all know youtube has it's fair share of issues and history in that area. But I've never seen it so crippled like it has been lately. During primetime my download speed to youtube will drop to 300KiloBITS per second. The whole internet feel's more and more congested. And if you haven't been living under a rock or you don't like in the US their is a bit of a war going on with ISP's, tier 3 ISP's, and you got the government compounding the issue. You've got this whole netflix thing going on. You've got these huge corporations wanting to keep their monopoly, to increase prices, and reduce costs by literally not upgrading the infrastructure.

Not to mention I see it happening in my own backyard and have been for years. I've had the same speeds for over a decade now. I've got two ISP's to choose from my local cable company who would make comcast's customer service look the best since sliced bread. Then I have AT&T and I only have them because they provide DSL. No other cable company has ever been allowed to provide TV or internet services. And AT&T is honestly a joke. Granted compared to my local cable company they are heroes. It wasn't until about a year ago that they started to install some new hardware for the first time in a decade. They have been done with that for at least the past 5 months. A guy was working on the lines one day and I pulled over to talk to him. He bluntly told me "Yea everythings done but their wanting to wait to turn it on sometime in the Fall". For what reason he had no clue. But a few months ago they decided to up price of the bill again. Like really? I've been paying you long enough for the same crappy connection to cover for upgrading the entire street. And more than likely it won't be a free or slight cost to upgrade the connection. I will probably have to pay twice as much.

What caused them to finally upgrade? That's a very good question they do provide the servers for my local cable company and on the 5mbit down connection they offer probably wasn't enough to keep up with the competition (like DirectTV).

That's a really long post. The internet is only going to get worse and worse until the average person starts to notice. And that will be the collapse of these greedy ISP's. But I fear that's going to take longer than expected. The average person at least where I live seems completely clueless about the internet. Or more accurately most people where I live are completely clueless. What's worse is when you try to educate them on the issue. Apparently people don't like to be educated. The only time they care to listen is when crap hits the fan and by that I mean (they can't get on facebook, or watch netflix, or youtube won't stop buffering, or they're connection keeps dropping). Then they're all ears. Sadly they just get angry and call AT&T and yell at some poor call center person who can't do anything about it anyways as their just a peon in the company in the grand scheme of things sadly.

it doesn't, you don't understand what i'm saying here. if finland to stockholm is 203ms, and finland to vegas (via stockholm) is also 203ms, there's not actually that latency to stockholm (otherwise you would see the cumulative affect at the end - which would be like 400ms!).

if you are playing on servers half way around the world - you can't complain about latency. end of.

what we are saying about thr 10k ping, that's something the game client is reporting and no one other than SOE know what it's doing to calculate that. the actualy latency through the network, on a network level is not 10 seconds. if it were you would probably be losing connection already and the anti cheat hit detection system wouldnt register a single one of your hits due to them being impossible shots at the time.

DNS just gives you the end IP address, it can't change your route to an IP. If you don't get that please go away.

Network level routing doesn't know what a dns name is.

Location Germany.
Poor quality connection, ~200ms Ping. Mostly a primetime issue.

I dont bother posting a tracert. This Level3 problems are known for at least 4 years. ISP basically said it was Level3s fault back then, so it is the same old problem again. Back then it took them months to solve the problem.

If Level3 really is in any way involved in this NSA surveillance state (like mentioned in this thread) wouldnt it be all the more a reason to not work together with them anymore?
Isnt there any alternative to Level3?

West Sussex, UK.

Code:

Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  BTHomeHub.home [192.168.1.254]
  2    *        *        *    Request timed out.
  3    *        *        *    Request timed out.
  4    16 ms    16 ms    15 ms  217.41.216.13
  5    15 ms    15 ms    14 ms  213.120.176.18
  6    15 ms    16 ms    15 ms  213.120.178.67
  7    16 ms    16 ms    14 ms  217.41.168.107
  8    16 ms    16 ms    17 ms  109.159.249.64
  9    15 ms    15 ms    15 ms  core2-te0-15-0-17.faraday.ukcore.bt.net [109.159.249.27]
10    19 ms    19 ms    19 ms  core2-Te0-0-0-2.ealing.ukcore.bt.net [213.121.193.70]
11    16 ms    66 ms    16 ms  transit2-xe11-1-0.ealing.ukcore.bt.net [194.72.17.194]
12    16 ms    16 ms    16 ms  t2c4-xe-9-0-0-0.uk-eal.eu.bt.net [166.49.168.49]
<--- Post-ISP from here --->
13    16 ms    17 ms    17 ms  xe-8-0-0.edge4.London2.Level3.net [212.187.192.61]
14  164 ms  163 ms  161 ms  vl-3202-ve-130.ebr2.London2.Level3.net [4.69.202.181]
15  202 ms  196 ms  195 ms  ae-42-42.ebr1.Paris1.Level3.net [4.69.159.86]
16  164 ms  160 ms  160 ms  ae-61-61.csw1.Paris1.Level3.net [4.69.161.78]
17  165 ms  162 ms  165 ms  ae-62-62.ebr2.Paris1.Level3.net [4.69.161.93]
18  200 ms  179 ms  175 ms  ae-44-44.ebr2.Washington1.Level3.net [4.69.137.6
2]
19  181 ms  179 ms  180 ms  ae-82-82.csw3.Washington1.Level3.net [4.69.134.1
54]
20  188 ms  179 ms  186 ms  ae-81-81.ebr1.Washington1.Level3.net [4.69.134.1
37]
21    *        *        *    Request timed out.
22  159 ms  160 ms  160 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
23  160 ms  160 ms  159 ms  ae-93-93.csw4.Dallas1.Level3.net [4.69.151.169]
 
24  159 ms  159 ms  162 ms  ae-92-92.ebr2.Dallas1.Level3.net [4.69.151.166]
 
25  160 ms  160 ms  160 ms  ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
26  187 ms  160 ms  160 ms  ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
27  161 ms  160 ms  162 ms  ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
 
28  160 ms  160 ms  160 ms  SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
29  160 ms  159 ms  160 ms  lp.soe.com [64.37.171.24]
 
Trace complete.
 

I'm not going to lie, I haven't read the whole thread, but I did see people talking about a method of not routing through level3. anyone confirm/deny?

Virginia, Comcast ISP and I play on Connery.

Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:

1 50 ms 47 ms 44 ms 24.125.14.1
2 51 ms 64 ms 17 ms xe-7-0-0-32767-sur01.sterling.va.richmond.comcast.net [68.85.70.37]
3 28 ms 37 ms 18 ms xe-7-0-0-0-ar02.charlvilleco.va.richmond.comcast.net [69.139.206.69]
4 * 24 ms 19 ms pos-1-3-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.57]
5 25 ms 39 ms 38 ms 23.30.207.94
6 108 ms 84 ms 147 ms vlan51.ebr1.Washington12.Level3.net [4.69.146.190]
7 86 ms 113 ms 100 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
8 * * * Request timed out.
9 110 ms 97 ms 92 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
10 86 ms 100 ms 89 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]
11 86 ms 83 ms 96 ms ae-82-82.ebr2.Dallas1.Level3.net [4.69.151.154]
12 * 116 ms 85 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
13 94 ms 89 ms 104 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
14 98 ms 94 ms 129 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
15 96 ms 84 ms 103 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
16 83 ms 97 ms 85 ms lp.soe.com [64.37.171.24]

Trace complete.


Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:

1 29 ms 30 ms 57 ms 24.125.14.1
2 837 ms * * xe-7-0-0-32767-sur01.sterling.va.richmond.comcast.net [68.85.70.37]
3 * 796 ms 506 ms xe-7-0-0-0-ar02.charlvilleco.va.richmond.comcast.net [69.139.206.69]
4 * 112 ms 48 ms pos-1-4-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.21]
5 * * * Request timed out.
6 * 1146 ms * vlan51.ebr1.Washington12.Level3.net [4.69.146.190]
7 * 189 ms 123 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
8 * * * Request timed out.
9 * * * Request timed out.
10 97 ms 87 ms 104 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]
11 100 ms 89 ms * ae-82-82.ebr2.Dallas1.Level3.net [4.69.151.154]
12 1397 ms 1149 ms 842 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
13 283 ms 83 ms 132 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
14 94 ms 101 ms 114 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
15 90 ms 92 ms 89 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
16 86 ms 107 ms 90 ms lp.soe.com [64.37.171.24]

Trace complete.


Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:

1 32 ms 37 ms 40 ms 24.125.14.1
2 19 ms 31 ms 18 ms xe-7-0-0-32767-sur01.sterling.va.richmond.comcast.net [68.85.70.37]
3 41 ms 67 ms 21 ms xe-7-0-0-0-ar02.charlvilleco.va.richmond.comcast.net [69.139.206.69]
4 23 ms 21 ms 44 ms pos-1-6-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.87.21]
5 52 ms 30 ms 41 ms 23.30.207.94
6 89 ms * 935 ms vlan51.ebr1.Washington12.Level3.net [4.69.146.190]
7 95 ms 87 ms 85 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
8 * * * Request timed out.
9 87 ms 89 ms 82 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
10 85 ms 109 ms 83 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]
11 86 ms 95 ms 100 ms ae-82-82.ebr2.Dallas1.Level3.net [4.69.151.154]
12 85 ms 81 ms 101 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
13 85 ms 83 ms 94 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
14 84 ms 91 ms 97 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
15 119 ms 85 ms * SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
16 82 ms 91 ms 99 ms lp.soe.com [64.37.171.24]

Trace complete.

I'm not tech or computer savvy but it looks like in the second trace I got massive spikes in both my ISP and L3.

Seattle, Washington, USA. Several hours today a single internal L3 server added +110ms to my ping. (doubled it) to Connery:
First:

Tracing route to lvspsn-liv-gw01.station.sony.com [64.37.174.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 1 ms 1 ms <1 ms 192.168.0.1
3 18 ms 19 ms 18 ms tukw-dsl-gw67.tukw.qwest.net [63.231.10.67]
4 18 ms 17 ms 17 ms tukw-agw1.inet.qwest.net [71.217.186.17]
5 19 ms 19 ms 20 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
6 25 ms 23 ms 21 ms ae14.edge2.Seattle1.Level3.net [4.68.62.189]
7 141 ms 138 ms 142 ms ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150]

8 146 ms 147 ms 147 ms ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49]
9 136 ms 141 ms 146 ms ae-2-2.ebr2.SanJose5.Level3.net [4.69.148.141]
10 148 ms 146 ms 142 ms ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201
]
11 142 ms 146 ms 147 ms ae-72-72.csw2.LosAngeles1.Level3.net [4.69.137.2
2]
12 145 ms 147 ms 145 ms ae-71-71.ebr1.LosAngeles1.Level3.net [4.69.137.5
]
13 156 ms 143 ms 144 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

14 143 ms 146 ms 148 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
15 143 ms 145 ms 155 ms vl3101.lvssw-1.sonyonline.net [64.37.168.6]
16 145 ms 139 ms 138 ms lvspsn-liv-gw01.station.sony.com [64.37.174.140]


Trace complete.

and an hour or so later:


Tracing route to lvspsn-liv-gw01.station.sony.com [64.37.174.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 1 ms 1 ms 1 ms 192.168.0.1
3 18 ms 19 ms 18 ms tukw-dsl-gw67.tukw.qwest.net [63.231.10.67]
4 18 ms 18 ms 18 ms tukw-agw1.inet.qwest.net [71.217.186.17]
5 19 ms 18 ms 18 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
6 25 ms 24 ms 25 ms ae14.edge2.Seattle1.Level3.net [4.68.62.189]
7 147 ms 142 ms 139 ms ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150]

8 134 ms 135 ms 142 ms ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49]
9 145 ms 136 ms 133 ms ae-2-2.ebr2.SanJose5.Level3.net [4.69.148.141]
10 143 ms 141 ms 142 ms ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201
]
11 146 ms 146 ms 147 ms ae-72-72.csw2.LosAngeles1.Level3.net [4.69.137.2
2]
12 141 ms 142 ms 146 ms ae-71-71.ebr1.LosAngeles1.Level3.net [4.69.137.5
]
13 144 ms 146 ms 148 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

14 148 ms 148 ms 146 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
15 149 ms 146 ms 141 ms vl3101.lvssw-1.sonyonline.net [64.37.168.6]
16 142 ms 139 ms 140 ms lvspsn-liv-gw01.station.sony.com [64.37.174.140]


Trace complete.

I should note that my issues resolved themselves by 11pm

Like every day, prime time is unplayable again. Do we have any word if SOE will get in contact with Level3 about this massive issue? MergeSmash is coming up and a lot of players can't play because of these massive latency and packet loss issues on those Level3 Gateways.

WE okay, today ****** as f*ck...

Hoster Deutsche Telekom / Germany

C:\Windows\system32>tracert lp.soe.com

Routenverfolgung zu lp.soe.com [64.37.171.24]
über maximal 30 Hops:

1 <1 ms <1 ms <1 ms Speedport.ip [192.168.2.1]
2 20 ms 19 ms 20 ms 217.0.117.179
3 21 ms 23 ms 24 ms 87.186.197.86
4 23 ms 24 ms 23 ms f-ee5-i.F.DE.NET.DTAG.DE [62.154.14.246]
5 45 ms 45 ms 46 ms 62.157.250.70
6 180 ms 180 ms 180 ms vlan70.csw2.Frankfurt1.Level3.net [4.69.154.126]

7 181 ms 180 ms 181 ms ae-71-71.ebr1.Frankfurt1.Level3.net [4.69.140.5]

8 186 ms 184 ms 185 ms ae-46-46.ebr2.Paris1.Level3.net [4.69.143.138]
9 187 ms 186 ms 186 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5
0]
10 182 ms 182 ms 182 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
11 186 ms 188 ms 189 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.1
33]
12 * * * Zeitüberschreitung der Anforderung.
13 188 ms 187 ms 187 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
14 188 ms 187 ms 187 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

15 185 ms 182 ms 183 ms ae-82-82.ebr2.Dallas1.Level3.net [4.69.151.154]

16 189 ms 187 ms 187 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
17 182 ms 182 ms 193 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
18 192 ms 187 ms 187 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

19 188 ms 188 ms 187 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
20 184 ms 184 ms 185 ms lp.soe.com [64.37.171.24]