Level3 issues? Post some info here

Discussion in 'Official News and Announcements' started by d_carey, Jul 12, 2014.

Thread Status:
Not open for further replies.
  1. TheAltoonaWiseman

    remember when you voted to legalize pot in colorado? you didint take into account a few things--
    the guy you give your money to at the bank, the pilots that fly over your house,..............
    and the guy that keeps the level3 servers running!.
  2. Partybooper

    I'm living 60km from Frankfurt, Germany. This is a traceroute to the Ceres server:

    Almost unplayable during prime time from around 5pm to midnight CET. Ingame ping varies between 170ms and 600ms, Connection quality often reads BAD. Packet loss makes it even worse.

    And here's the netinfo I attached to my support ticket for SOE. ;)

    https://help.soe.com/ci/fattach/get/1317507/1405013212/filename/netinfo.txt
  3. Sid6dot7

    Code:
    tracert 69.174.194.167
     
    Routenverfolgung zu amspsn-liv-gw03.planetside2.com [69.174.194.167] über maximal 30 Abschnitte:
     
    1    <1 ms  <1 ms    <1 ms  router.asus.com [192.168.0.1]
    2    44 ms  43 ms    43 ms  87.186.224.213
    3    46 ms  46 ms    61 ms  87.190.191.54
    4    51 ms  56 ms    54 ms  b-ea7-i.B.DE.NET.DTAG.DE [62.154.46.186]
    5    49 ms  53 ms    51 ms  62.157.251.238
    6    140 ms  139 ms  143 ms  ae-34-52.ebr2.Berlin1.Level3.net [4.69.146.153]
    7    143 ms  143 ms  140 ms  ae-26-26.ebr2.Dusseldorf1.Level3.net [4.69.200.165]
    8    138 ms  137 ms  135 ms  ae-45-45.ebr1.Amsterdam1.Level3.net [4.69.143.197]
    9    136 ms  136 ms  138 ms  ae-56-111.csw1.Amsterdam1.Level3.net [4.69.153.186]
    10  140 ms  140 ms  134 ms  4.69.162.166
    11  145 ms  132 ms  127 ms  SONY-ONLINE.edge3.Amsterdam1.Level3.net [212.72.33.26]
    12  138 ms  165 ms  151 ms  amspsn-liv-gw03.planetside2.com [69.174.194.167]

    #4 DTAG is my ISP (europe, east germany).
    Around 3pm and 11pm local time (UTC+2), but mostly through primetime, I get a ping increase of ~100ms between #5 and #12. If the connection is ok, none of above traceroute lines goes over 69ms.
    The ping increase wouldn't be the problem (ingame ping ~200ms), but the connection itself is unreliable. I get huge lags and ping spikes when playing PS2 and PS2's connection indicator always shows yellow and sometimes red.
  4. Jatz

    Location: Colorado

    Problems: Occasionally spiking from 150-300+ ping (Sometimes in excess of 500+ for short periods.)
    Not at all that frequently, once or twice a day.

    Trace:

    Just following the trend >_>
  5. Zenkari

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

    1 <1 ms <1 ms <1 ms router.Ascension [192.168.2.1]
    2 3 ms 2 ms 1 ms 10.0.0.1
    3 13 ms 10 ms 9 ms c-73-181-124-1.hsd1.co.comcast.net [73.181.124.1]
    4 15 ms 16 ms 47 ms te-5-4-ur01.longmont.co.denver.comcast.net [68.86.104.233]
    5 10 ms 9 ms 9 ms te-8-4-ur02.longmont.co.denver.comcast.net [68.86.103.162]
    6 26 ms 18 ms 13 ms xe-14-0-0-0-ar01.aurora.co.denver.comcast.net [162.151.8.1]
    7 16 ms 15 ms 22 ms he-3-9-0-0-cr01.denver.co.ibone.comcast.net [68.86.92.21]
    8 13 ms 15 ms 13 ms ae14.edge3.Denver1.Level3.net [4.68.127.129]
    9 41 ms 41 ms 43 ms vlan51.ebr1.Denver1.Level3.net [4.69.147.94]
    10 68 ms 76 ms 42 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    11 45 ms 42 ms 43 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    12 44 ms 43 ms 48 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    13 45 ms 45 ms 56 ms lp.soe.com [64.37.171.24]
  6. DNOMINATOR

    Don't know if this is related but for some reason I cant get into the game. It keeps bringing up an error every time I try to upload the patch.
  7. BlanketSON

    Code:
    Tracing route to lp.soe.com [64.37.171.24]
    over a maximum of 30 hops:
     
    1    2 ms    2 ms    1 ms  192.168.1.254
    2    32 ms    29 ms    30 ms  99-9-232-3.lightspeed.mssnks.sbcglobal.net [99.9
    .232.3]
    3    33 ms    30 ms    28 ms  71.150.32.182
    4    31 ms    31 ms    30 ms  12.83.42.133
    5    45 ms    44 ms    44 ms  gar13.cgcil.ip.att.net [12.122.132.121]
    6    *        *        *    Request timed out.
    7    82 ms    80 ms    81 ms  vl-3506-ve-120.ebr1.Chicago2.Level3.net [4.69.15
    8.134]
    8    82 ms    81 ms    82 ms  ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    9    81 ms    83 ms    82 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]
    10    80 ms    81 ms    81 ms  ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    11  334 ms  213 ms  220 ms  ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    12  168 ms  207 ms  137 ms  SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    13  184 ms  207 ms  209 ms  lp.soe.com [64.37.171.24]
    My in-game latency will have an increase of 300ms to 600ms from my normal latency of 90ms to 120ms every couple minutes with the connection quality progressing from good to poor to bad in the process. Level3 has really been messing with my ability to play the game.

    Location: Kansas City, MO
    AT&T: Uverse
  8. AlexLangley

    Code:
    Tracing route to lp.soe.com [64.37.171.24]
    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.5.1
      3    5 ms    3 ms    13 ms  10.0.42.1
      4    2 ms    3 ms    4 ms  10.10.1.10
      5    5 ms    5 ms    5 ms  10.10.8.161
      6    5 ms    5 ms    3 ms  10.10.1.13
      7    5 ms    10 ms    12 ms  185.6.154.1
      8    27 ms    8 ms    19 ms  te0-0-2-3.rcr11.lba01.atlas.cogentco.com [149.11.42.81]
      9    12 ms    13 ms    8 ms  te0-2-0-4.ccr21.lpl01.atlas.cogentco.com [154.54.37.150]
    10    81 ms  106 ms    78 ms  be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44.137]
    11    86 ms    87 ms    85 ms  be2090.ccr21.yyz02.atlas.cogentco.com [154.54.30.205]
    12    86 ms    91 ms    86 ms  level3.yyz02.atlas.cogentco.com [154.54.11.210]
    13    90 ms    85 ms    88 ms  ae-13-13.bar1.toronto1.level3.net [4.69.200.233]
    14  155 ms  173 ms  180 ms  ae-9-9.ebr1.chicago1.level3.net [4.69.151.110]
    15  149 ms  148 ms  149 ms  ae-6-6.ebr1.chicago2.level3.net [4.69.140.190]
    16  151 ms  154 ms  147 ms  ae-3-3.ebr2.denver1.level3.net [4.69.132.61]
    17  146 ms  158 ms  150 ms  ae-1-100.ebr1.denver1.level3.net [4.69.151.181]
    18  152 ms  147 ms  148 ms  ae-1-6.bar2.lasvegas1.level3.net [4.69.148.1]
    19  149 ms  151 ms  157 ms  ae-0-11.bar1.lasvegas1.level3.net [4.69.148.125]
    20  148 ms  152 ms  154 ms  switch-comm.bar1.lasvegas1.level3.net [205.129.16.50]
    21  148 ms  148 ms  148 ms  lp.soe.com [64.37.171.24]
     
    Trace complete.
    I'm in the U.K, used to be able to play without any problems but now my latency is 30,000-50,000 - completely unplayable.

    Update: Just tried playing on Emerald and got a latency of 29,117 - http://i62.tinypic.com/jzzatz.jpg.
  9. Munr

    Oh man, finally! SOE Support wanted me to go argue with my ISP but I know it was't all on my end.

    Here's some data!

    http://pastebin.com/yRm9ydEG

    Hope you guys root it out soon. I can't play with a 10,000 ms ping. (Seriously. From 82ms to over 10,000!)
  10. AssaultPig

    I'm not at home this weekend so I can't post traces, but I'm excited to see this finally getting some attention. Tired of seeing my ping spike up to 10k+ for no discernible reason.
  11. ironeddie

    These pings are crazy. Every single one is fine until it gets to level3. I'll check mine tomorrow. It's to late now.
  12. FourTwoFour

    I'm from Europe and I still get a ping of 60-70 instead of 30 like I do in let's say Battlefield or any other game (to servers in Germany or Holland). My ping usually spikes up to 150-250 whenever it feels like it. Sometimes I get connection status "bad" and it goes up to 50k or whatever, the game just goes crazy.

    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\Users\Fourzero>tracert lp.soe.com

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

    1 1 ms <1 ms <1 ms 87.118.178.1
    2 3 ms 3 ms 3 ms 212.116.146.169
    3 6 ms 3 ms 3 ms 162.97.150.121
    4 26 ms 26 ms 26 ms xe0-3-2-10G.scr4.FRA4.gblx.net [67.16.142.254]
    5 27 ms 27 ms 26 ms po6-10G.ar2.FRA4.gblx.net [209.130.130.226]
    6 28 ms 27 ms 27 ms ae-9-0.edge4.Frankfurt1.Level3.net [4.68.63.241]

    7 176 ms 176 ms 177 ms vlan90.csw4.Frankfurt1.Level3.net [4.69.154.254]

    8 175 ms 176 ms 175 ms ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13
    ]
    9 174 ms 174 ms 174 ms ae-46-46.ebr2.Paris1.Level3.net [4.69.143.138]
    10 182 ms 173 ms 173 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
    8]
    11 174 ms 175 ms 174 ms ae-47-47.ebr2.Washington12.Level3.net [4.69.202.
    58]
    12 174 ms 174 ms 174 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    13 175 ms 174 ms 174 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

    14 175 ms 174 ms 174 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    15 173 ms 174 ms 174 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    16 174 ms 174 ms 174 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    17 173 ms 173 ms 208 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    18 175 ms 174 ms 174 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    19 174 ms 174 ms 174 ms lp.soe.com [64.37.171.24]

    Trace complete.

    C:\Users\Fourzero>tracert lp.soe.com

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

    1 <1 ms <1 ms <1 ms 87.118.178.1
    2 3 ms 3 ms 3 ms 212.116.146.169
    3 4 ms 4 ms 14 ms 162.97.150.121
    4 27 ms 26 ms 26 ms xe0-3-2-10G.scr4.FRA4.gblx.net [67.16.142.254]
    5 27 ms 28 ms 26 ms po6-10G.ar2.FRA4.gblx.net [209.130.130.226]
    6 27 ms 27 ms 28 ms ae-9-0.edge4.Frankfurt1.Level3.net [4.68.63.241]

    7 176 ms 176 ms 176 ms vlan90.csw4.Frankfurt1.Level3.net [4.69.154.254]

    8 175 ms 175 ms 175 ms ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13
    ]
    9 175 ms 174 ms 174 ms ae-46-46.ebr2.Paris1.Level3.net [4.69.143.138]
    10 174 ms 173 ms 174 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
    8]
    11 173 ms 173 ms 173 ms ae-47-47.ebr2.Washington12.Level3.net [4.69.202.
    58]
    12 174 ms 174 ms 181 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    13 174 ms 173 ms 173 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

    14 175 ms 174 ms 174 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    15 181 ms 173 ms 174 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    16 175 ms 174 ms 175 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    17 173 ms 173 ms 173 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    18 175 ms 175 ms 174 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    19 174 ms 174 ms 174 ms lp.soe.com [64.37.171.24]

    Trace complete.

    C:\Users\Fourzero>
  13. snrcub224

    My Texan ISP uses mainly Hurricane Electric and Level3 for transit (HE for west-bound connections and L3 for east-bound connections). As an Emerald player, I get ~21ms latency to Emerald on good days and ~90ms latency on bad days. I've only had issues with Hurricane Electric, Level3 is pretty good for me.

    Got data:

    Tracing route to lp.soe.com [64.37.171.24]
    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.1.1
    3 1 ms 1 ms <1 ms srcwt-svf-ftth-gw0.srcwt-rtr0.smithville-tx.as19754.liveair.net [198.98.86.65]
    4 12 ms 6 ms 5 ms srcwt-q1582.1825a-rtr0.austin-tx.as19754.liveair.net [199.66.158.241]
    5 16 ms 15 ms 15 ms vlan125.car2.Houston1.Level3.net [4.31.169.21]
    6 17 ms 66 ms 15 ms ae-2-5.bar2.Houston1.Level3.net [4.69.132.238]
    7 19 ms 15 ms 15 ms ae-0-11.bar1.Houston1.Level3.net [4.69.137.133]
    8 53 ms 53 ms 53 ms ae-13-13.ebr1.Dallas1.Level3.net [4.69.137.138]
    9 53 ms 53 ms 53 ms ae-71-71.csw2.Dallas1.Level3.net [4.69.151.137]
    10 53 ms 54 ms 54 ms ae-72-72.ebr2.Dallas1.Level3.net [4.69.151.142]
    11 54 ms 54 ms 54 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
    12 54 ms 53 ms 53 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    13 53 ms 54 ms 53 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    14 54 ms 54 ms 54 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    15 54 ms 55 ms 54 ms lp.soe.com [64.37.171.24]

    Trace complete.
  14. DatName

    and another snippet from a traceroute to lp.soe.com
    Code:
    ...
      5    42 ms    40 ms    40 ms  62.157.250.70
      6  199 ms  199 ms  197 ms  vlan90.csw4.Frankfurt1.Level3.net [4.69.154.254]
    ...
     18   198 ms   198 ms   198 ms  lp.soe.com [64.37.171.24]
    
    starting from a DTAG connection near Frankfurt /Germany.

    Consider me "not happy" with the lag.
  15. snrcub224

    Level3 is an ISP in mostly central and SE US. I've never had any issues with them, and my ISP uses them as one of their primary transit hosts.
  16. snrcub224

    That does sound like an auth-server connection issue.
  17. Botji

    From Sweden and the problem is obviously the kinda high ping. Its playable but when you play on a EU server you dont expect a +100 ping response time to that server.

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

    1 1 ms 1 ms 1 ms h109-225-100-1.dynamic.se.alltele.net [109.225.100.1]
    2 <1 ms <1 ms <1 ms 217-17-65-193.link.pite.com [217.17.65.193]
    3 1 ms <1 ms <1 ms 217-17-71-130.link.pite.com [217.17.71.130]
    4 <1 ms <1 ms <1 ms v2062-0-ge-0-26.cr1.pit.se.alltele.net [79.138.0.229]
    5 1 ms 1 ms 1 ms v2044-0-te-4-1.cr1.lul.se.alltele.net [88.129.128.73]
    6 11 ms 11 ms 11 ms 62.209.173.245
    7 20 ms 20 ms 27 ms 62.109.44.69
    8 31 ms 31 ms 40 ms noosl0001-rc4.ip-only.net [62.109.44.106]
    9 30 ms 30 ms 30 ms noosl0001-rc3.ip-only.net [62.109.44.93]
    10 31 ms 40 ms 31 ms segot0001-rc3.ip-only.net [62.109.44.109]
    11 30 ms 49 ms 31 ms segot0001-rc2.ip-only.net [62.109.44.113]
    12 35 ms 35 ms 35 ms xe-10-1-1.bar1.Copenhagen1.Level3.net [213.242.108.85]
    13 197 ms 199 ms 199 ms ae-7-7.ebr1.Dusseldorf1.Level3.net [4.69.142.170]
    14 194 ms 194 ms 194 ms ae-45-45.ebr3.Frankfurt1.Level3.net [4.69.143.166]
    15 196 ms 197 ms 195 ms ae-93-93.csw4.Frankfurt1.Level3.net [4.69.163.14]
    16 198 ms 198 ms 198 ms ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13]
    17 196 ms 196 ms 196 ms ae-46-46.ebr2.Paris1.Level3.net [4.69.143.138]
    18 197 ms 197 ms 197 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.58]
    19 195 ms 195 ms 195 ms ae-48-48.ebr2.Washington12.Level3.net [4.69.202.62]
    20 195 ms 195 ms 195 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    21 196 ms 197 ms 196 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
    22 197 ms 197 ms 198 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    23 195 ms 195 ms 196 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]
    24 227 ms 196 ms 196 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    25 195 ms 221 ms 195 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    26 196 ms 196 ms 196 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    27 194 ms 195 ms 195 ms lp.soe.com [64.37.171.24]

    Trace complete.
  18. aceoyame

    Here is my trace. Not sure why I have so many timeouts between Level 3's various points.

    As you can see Verizon Wireless is my ISP as I use my phone tethered to provide internet to the house (Droid RAZR HD MAXX)

    C:\Users\aceoyame>tracert lp.soe.com

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

    1 <1 ms <1 ms 1 ms E2000 [10.191.161.65]
    2 8 ms 11 ms 4 ms 192.168.1.1
    3 14 ms 5 ms 18 ms 192.168.43.1
    4 63 ms 57 ms 60 ms 121.sub-66-174-53.myvzw.com [66.174.53.121]
    5 50 ms 54 ms 60 ms 146.sub-69-83-68.myvzw.com [69.83.68.146]
    6 63 ms 51 ms 69 ms 113.sub-69-83-81.myvzw.com [69.83.81.113]
    7 54 ms 63 ms 59 ms 81.sub-69-83-81.myvzw.com [69.83.81.81]
    8 67 ms 79 ms 66 ms 162.sub-69-83-68.myvzw.com [69.83.68.162]
    9 66 ms 61 ms 70 ms 4.sub-69-83-64.myvzw.com [69.83.64.4]
    10 * * * Request timed out.
    11 66 ms 69 ms 69 ms 97.sub-69-83-82.myvzw.com [69.83.82.97]
    12 67 ms 79 ms 70 ms ip65-46-44-237.z44-46-65.customer.algx.net [65.
    6.44.237]
    13 * * * Request timed out.
    14 * 85 ms 59 ms 207.88.14.194.ptr.us.xo.net [207.88.14.194]
    15 88 ms 80 ms 79 ms ae8.edge3.Chicago3.Level3.net [4.68.127.245]
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 116 ms 120 ms 119 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125

    21 129 ms 129 ms 125 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.
    6.50]
    22 176 ms 179 ms 119 ms lp.soe.com [64.37.171.24]
  19. DiReis

    This is mine:

    I'm from Brazil and I've been having lots of issues lately.. my ping usually goes from 200ms (which, usually, is the average for me..) to 5s or worst.. :( almost unplayable..

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

    1 <1 ms <1 ms <1 ms DD-WRT [10.0.0.1]
    2 * * * Request timed out.
    3 2 ms 2 ms 4 ms 201-0-87-253.dsl.telesp.net.br [201.0.87.253]
    4 5 ms 3 ms 5 ms 201-0-5-65.dsl.telesp.net.br [201.0.5.65]
    5 4 ms 4 ms 3 ms 200-100-98-89.dial-up.telesp.net.br [200.100.98.89]
    6 17 ms 17 ms 16 ms et-6-0-0-101-GRTRIOTW2.red.telefonica-wholesale.net [84.16.9.65]
    7 121 ms 119 ms 118 ms Hu1-1-0-0-0-grtmiabr6.red.telefonica-wholesale.net [5.53.3.149]
    8 147 ms 147 ms 146 ms Xe-0-0-2-0-grtdaleq4.red.telefonica-wholesale.net [176.52.251.49]
    9 160 ms 159 ms 206 ms xe-10-2-0.edge5.Dallas3.Level3.net [4.59.36.53]
    10 194 ms 202 ms 192 ms vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
    11 201 ms 202 ms 201 ms ae-92-92.ebr2.Dallas1.Level3.net [4.69.151.166]
    12 195 ms 193 ms 194 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
    13 194 ms 250 ms 193 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    14 196 ms 194 ms 194 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    15 194 ms 197 ms 195 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    16 204 ms 204 ms 202 ms lp.soe.com [64.37.171.24]

    Trace complete.
  20. Xebov

    Where did you guys get the Server adresses from? I would liek to do a trace myself but i dont know the IPs/Adresses from the Servers.
Thread Status:
Not open for further replies.