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.
Page 6 of 23

  1. JHz

    Removed personally identifying information. Tested from three locations, first is San Diego, CA, second is Dallas, TX, third is Philadelphia, PA.

    C:\Windows\system32>tracert 64.37.171.24

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

    1 1 ms <1 ms <1 ms *REMOVED*
    2 1 ms 1 ms 1 ms 192.168.1.254
    3 1 ms 1 ms 1 ms *REMOVED*
    4 19 ms 19 ms 19 ms 75.20.78.152
    5 21 ms 19 ms 19 ms 12.83.70.149
    6 23 ms 23 ms 23 ms ggr2.la2ca.ip.att.net [12.122.129.105]
    7 23 ms 22 ms 23 ms 192.205.37.146
    8 29 ms 29 ms 31 ms vl-3507-ve-121.ebr1.Tustin1.Level3.net [4.69.158.105]
    9 29 ms 29 ms 29 ms ae-6-6.ebr1.LosAngeles1.Level3.net [4.69.153.221]
    10 29 ms 29 ms 29 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
    11 29 ms 30 ms 29 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    12 29 ms 31 ms 29 ms lp.soe.com [64.37.171.24]

    Trace complete.

    C:\Windows\system32>tracert 64.37.171.24

    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.2
    2 <1 ms <1 ms <1 ms *REMOVED* [*REMOVED*]
    3 <1 ms <1 ms <1 ms *REMOVED* [*REMOVED*]
    4 1 ms 1 ms 1 ms te0-0-1-0.nr11.b000326-4.dfw05.atlas.cogentco.com [38.122.56.37]
    5 1 ms <1 ms 1 ms 154.24.22.9
    6 1 ms 1 ms 1 ms te2-3.mag02.dfw03.atlas.cogentco.com [154.54.1.61]
    7 1 ms 1 ms 1 ms te0-1-0-2.ccr22.dfw03.atlas.cogentco.com [154.54.81.37]
    8 1 ms 1 ms 1 ms be2033.ccr21.dfw03.atlas.cogentco.com [154.54.25.5]
    9 1669 ms 1894 ms 1498 ms lag-42.ear1.dallas1.level3.net [4.68.111.101] LOL WUT?
    10 41 ms 41 ms 41 ms vl-3502-ve-116.csw1.dallas1.level3.net [4.69.146.5]
    11 41 ms 41 ms 41 ms ae-62-62.ebr2.dallas1.level3.net [4.69.151.130]
    12 41 ms 41 ms 41 ms ae-2-2.ebr1.denver1.level3.net [4.69.132.105]
    13 41 ms 41 ms 41 ms ae-1-6.bar2.lasvegas1.level3.net [4.69.148.1]
    14 41 ms 41 ms 41 ms ae-0-11.bar1.lasvegas1.level3.net [4.69.148.125]
    15 41 ms 41 ms 41 ms switch-comm.bar1.lasvegas1.level3.net [205.129.16.50]
    16 42 ms 41 ms 42 ms lp.soe.com [64.37.171.24]

    Trace complete.

    C:\windows\system32>tracert 64.37.171.24

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

    1 <1 ms <1 ms 1 ms *REMOVED*
    2 <1 ms <1 ms <1 ms xe-7-2-3.bar1.Philadelphia1.Level3.net [4.34.195.129]
    3 62 ms 62 ms 62 ms ae-3-3.ebr1.Washington1.Level3.net [4.69.133.162]
    4 62 ms 62 ms 62 ms ae-8-8.ebr1.Washington12.Level3.net [4.69.143.218]
    5 62 ms 62 ms 62 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]
    6 62 ms 62 ms 62 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    7 63 ms 63 ms 62 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
    8 60 ms 62 ms 60 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    9 61 ms 61 ms 61 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]
    10 61 ms 61 ms 61 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    11 61 ms 61 ms 61 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    12 62 ms 62 ms 62 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    13 61 ms 61 ms 61 ms lp.soe.com [64.37.171.24]

    Trace complete.
    JHz, Jul 13, 2014
    #101

  2. JHz

    One more, this is Buffalo, NY.

    *@*:~$ traceroute 64.37.171.24
    traceroute to 64.37.171.24 (64.37.171.24), 30 hops max, 60 byte packets
    1 *REMOVED* (*REMOVED*) 0.092 ms 0.015 ms 0.013 ms
    2 *REMOVED* (*REMOVED*) 0.681 ms 0.670 ms 0.653 ms
    3 *REMOVED* (*REMOVED*) 0.144 ms *REMOVED* (*REMOVED*) 0.162 ms *REMOVED* (*REMOVED*) 0.148 ms
    4 *REMOVED* (*REMOVED*) 0.166 ms *REMOVED* (*REMOVED*) 0.187 ms *REMOVED* (*REMOVED*) 0.173 ms
    5 216.156.0.253.ptr.us.xo.net (216.156.0.253) 14.207 ms 216.156.1.126.ptr.us.xo.net (216.156.1.126) 13.152 ms 216.156.0.253.ptr.us.xo.net (216.156.0.253) 14.099 ms
    6 * * 216.156.0.253.ptr.us.xo.net (216.156.0.253) 14.505 ms
    7 ae8.edge3.Chicago3.Level3.net (4.68.127.245) 13.077 ms 13.064 ms 12.992 ms
    8 vlan51.ebr1.Chicago2.Level3.net (4.69.138.158) 62.401 ms 62.379 ms 62.300 ms
    9 vlan51.ebr1.Chicago2.Level3.net (4.69.138.158) 62.411 ms ae-3-3.ebr2.Denver1.Level3.net (4.69.132.61) 62.476 ms vlan51.ebr1.Chicago2.Level3.net (4.69.138.158) 62.436 ms
    10 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 62.345 ms 62.336 ms ae-3-3.ebr2.Denver1.Level3.net (4.69.132.61) 62.642 ms
    11 ae-1-6.bar2.LasVegas1.Level3.net (4.69.148.1) 75.286 ms 62.977 ms ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 62.333 ms
    12 ae-0-11.bar1.LasVegas1.Level3.net (4.69.148.125) 62.651 ms 62.598 ms 62.769 ms
    13 SWITCH-COMM.bar1.LasVegas1.Level3.net (205.129.16.50) 62.393 ms 63.004 ms ae-0-11.bar1.LasVegas1.Level3.net (4.69.148.125) 62.780 ms
    14 SWITCH-COMM.bar1.LasVegas1.Level3.net (205.129.16.50) 63.145 ms 63.201 ms 63.313 ms
    15 * *^C
    JHz, Jul 13, 2014
    #102

  3. Merijn

    Code:
      3    12 ms    7 ms    8 ms  venl-rc0003-cr102-xe-0-2-2-0.core.as9143.net [213.51.187.58]
  4    11 ms    14 ms    39 ms  asd-tr0610-cr101-ae0-0.core.as9143.net [213.51.160.216]
  5    11 ms    15 ms    13 ms  te0-0-1-2.nr12.b038092-0.ams03.atlas.cogentco.com [149.11.65.37]
  6    14 ms    15 ms    21 ms  154.25.2.185
  7    15 ms    13 ms    11 ms  be2434.ccr41.ams03.atlas.cogentco.com [130.117.2.242]
  8    24 ms    26 ms    21 ms  be2182.ccr21.lpl01.atlas.cogentco.com [154.54.77.246]
  9    93 ms    93 ms    92 ms  be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44.137]
10  102 ms  105 ms    99 ms  be2090.ccr21.yyz02.atlas.cogentco.com [154.54.30.205]
11    *      160 ms    *    level3.yyz02.atlas.cogentco.com [154.54.11.210]
12  102 ms  100 ms  105 ms  ae-13-13.bar1.Toronto1.Level3.net [4.69.200.233]
13  171 ms  156 ms  160 ms  ae-9-9.ebr1.Chicago1.Level3.net [4.69.151.110]
14  159 ms    *      156 ms  ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
15  167 ms    *      155 ms  ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
16  156 ms  166 ms  162 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]
17  155 ms  157 ms  156 ms  ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
18  156 ms  154 ms  163 ms  ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
19  155 ms  157 ms  155 ms  SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
20  156 ms  156 ms  159 ms  lp.soe.com [64.37.171.24]
    Some PL
    Merijn, Jul 13, 2014
    #103

  4. GingerGrinch

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

    1 9 ms 7 ms 8 ms 10.159.200.1
    2 9 ms 9 ms 9 ms brad-core-2b-ae9-718.network.virginmedia.net
    .97.82.169]
    3 13 ms 11 ms 11 ms leed-bb-1b-ae6-0.network.virginmedia.net [81.
    80.121]
    4 25 ms 44 ms 48 ms leed-bb-2a-ae2-0.network.virginmedia.net [62.
    .42.121]
    5 * 506 ms * leed-bb-1c-ae0-0.network.virginmedia.net [62.
    .42.126]
    6 15 ms 16 ms 16 ms 213.152.245.53
    7 25 ms 18 ms 25 ms ae11.mpr1.lhr1.uk.above.net [64.125.27.49]
    8 16 ms 21 ms 52 ms 4.68.70.77
    9 731 ms 448 ms 220 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.
    .153]
    10 157 ms 152 ms 153 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.1

    11 150 ms 154 ms 176 ms ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.7

    12 150 ms 163 ms 152 ms ae-48-48.ebr1.NewYork2.Level3.net [4.69.201.5

    13 153 ms 154 ms 172 ms ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.2

    14 157 ms 152 ms 153 ms ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
    15 154 ms 163 ms 161 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190
    16 154 ms 151 ms 154 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    17 473 ms 411 ms 369 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.18

    18 160 ms 151 ms 151 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    19 151 ms 153 ms 151 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.1

    20 353 ms 199 ms 199 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.12
    6.50]
    21 157 ms 148 ms 149 ms lp.soe.com [64.37.171.24]

    Trace complete.
    GingerGrinch, Jul 13, 2014
    #104

  5. ironeddie

    So according to the in game latency connection gauge thingimy bob I'm usually at about 50 to 70ms but it spikes to 200+ms

    So I'm in the UK and I've run tracert to woodman and it's fine, ran tracert to lp.soe.com and it goes fubar. The difference between the two? Well from me to woodman I don't go through a level 3 switch. I do on my way to lp.soe.com. So this neatly shows how the problem is clearly with level 3.

    What I don't get is why my latency sometimes spikes really badly. Perhaps my data packets are occasionally being redirected through level 3? I dunno.

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

    C:\WINDOWS\system32>tracert 69.174.194.168

    Tracing route to amspsn-liv-gw04.planetside2.com [69.174.194.168]
    over a maximum of 30 hops:

    1 9 ms 11 ms 11 ms 10.66.184.1
    2 14 ms 14 ms 14 ms perr-core-2b-xe-301-0.network.virginmedia.net [8
    0.1.69.237]
    3 552 ms 62 ms 41 ms brhm-bb-1c-ae14-0.network.virginmedia.net [62.25
    5.149.69]
    4 * 23 ms 15 ms brhm-bb-2a-ae3-0.network.virginmedia.net [62.254
    .42.109]
    5 19 ms 18 ms 20 ms nrth-bb-2a-ae4-0.network.virginmedia.net [62.254
    .42.46]
    6 15 ms 19 ms 16 ms nrth-bb-1b-ae0-0.network.virginmedia.net [62.254
    .42.130]
    7 17 ms 18 ms 18 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253.
    174.18]
    8 19 ms 20 ms 18 ms linx-224.bg2.ld2.eu.equinix.net [195.66.224.187]

    9 22 ms 20 ms 20 ms po3.bg1.ld2.eu.equinix.net [80.69.1.221]
    10 38 ms 26 ms 26 ms po9-1405.bg1.am1.eu.equinix.net [89.187.106.154]

    11 172 ms 26 ms 26 ms po7.bg1.am3.eu.equinix.net [94.103.16.86]
    12 101 ms 25 ms 26 ms sony.customer.am3.eu.equinix.net [5.175.82.90]
    13 51 ms 24 ms 22 ms amspsn-liv-gw04.planetside2.com [69.174.194.168]


    Trace complete.

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

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

    1 198 ms 73 ms 68 ms 10.66.184.1
    2 11 ms 13 ms 11 ms perr-core-2a-xe-301-0.network.virginmedia.net [8
    0.1.69.233]
    3 14 ms 14 ms 16 ms manc-bb-1c-ae5-0.network.virginmedia.net [62.255
    .149.65]
    4 14 ms 15 ms 14 ms ae0.man11.ip4.tinet.net [77.67.65.141]
    5 28 ms 28 ms 28 ms xe-7-0-2.lon10.ip4.tinet.net [141.136.107.9]
    6 76 ms 20 ms 19 ms ae8.edge4.London.Level3.net [4.68.111.25]
    7 156 ms 157 ms 158 ms vl-3608-ve-232.csw2.London1.Level3.net [4.69.166
    .30]
    8 157 ms 156 ms 156 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]

    9 159 ms 160 ms 159 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

    10 156 ms 156 ms 157 ms ae-48-48.ebr1.NewYork2.Level3.net [4.69.201.50]

    11 157 ms 156 ms 158 ms ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]

    12 160 ms 158 ms 158 ms ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
    13 155 ms 159 ms 155 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
    14 157 ms 157 ms 156 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    15 155 ms 156 ms 156 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    16 159 ms 159 ms 162 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    17 157 ms 157 ms 156 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    18 156 ms 156 ms 156 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    19 154 ms 152 ms 152 ms lp.soe.com [64.37.171.24]

    Trace complete.
    ironeddie, Jul 13, 2014
    #105

  6. Snoozzzer

    Living on the east coast, currently using optimum and going from ok to good to not so ok lag
    Snoozzzer, Jul 13, 2014
    #106

  7. DrDeathDefying

    Here's my tracert from Quincy, MA - a few clicks south of Boston.
    This is the second one I've run - surprisingly, this one (which I decided to post) has considerably higher pings; the first tracert I ran had pings all in the teens.

    C:\Users\*censored*>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 10.0.0.1
    2 7 ms 9 ms 8 ms *censored*
    3 8 ms 9 ms 9 ms te-7-4-ur02.quincy.ma.boston.comcast.net [68.86.
    237.213]
    4 8 ms 9 ms 12 ms po-20-ur01.quincy.ma.boston.comcast.net [68.87.1
    45.25]
    5 10 ms 27 ms 11 ms be-78-ar01.needham.ma.boston.comcast.net [68.87.
    145.21]
    6 28 ms 22 ms 15 ms he-2-6-0-0-cr01.newyork.ny.ibone.comcast.net [68
    .86.93.33]
    7 15 ms 14 ms 15 ms ae12.edge1.NewYork2.level3.net [4.68.127.1]
    8 75 ms 75 ms 75 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
    9 76 ms 76 ms 77 ms ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
    10 77 ms 78 ms 76 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
    11 75 ms 75 ms 76 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    12 76 ms 75 ms 76 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    13 76 ms 76 ms 92 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    14 75 ms 75 ms 77 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    15 90 ms 89 ms 88 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    16 90 ms 89 ms 88 ms lp.soe.com [64.37.171.24]

    Trace complete.
    DrDeathDefying, Jul 13, 2014
    #107

  8. THE Toad

    Hi, I'm in Brisbane, Australia.


    I did this tracert back in Apr 4 2014:

    tracert 64.37.174.140

    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 192.168.0.1
    2 <1 ms <1 ms <1 ms 192.168.1.1
    3 14 ms 14 ms 14 ms nexthop.qld.iinet.net.au [203.215.9.250]
    4 14 ms 15 ms 14 ms ae7.cr1.bne4.on.ii.net [150.101.33.158]
    5 50 ms 58 ms 48 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
    6 178 ms 177 ms 178 ms te0-1-1-2.br2.lax1.on.ii.net [203.16.213.190]
    7 * 177 ms * xe-7-0-3.edge2.LosAngeles9.Level3.net [4.53.230.45]
    8 * 211 ms 212 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190]
    9 * 182 ms 182 ms ae-81-81.ebr1.LosAngeles1.Level3.net [4.69.137.9]
    10 182 ms 182 ms 182 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
    11 183 ms 183 ms 183 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    12 212 ms 212 ms 212 ms vl3101.lvssw-1.sonyonline.net [64.37.168.6]
    13 183 ms 182 ms 183 ms lvspsn-liv-gw01.station.sony.com [64.37.174.140]


    This is my current result at time of posting

    tracert 64.37.174.140

    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 192.168.0.1
    2 <1 ms <1 ms <1 ms 192.168.1.1
    3 13 ms 13 ms 13 ms lo0.bne-pipe-bng2.iinet.net.au [203.215.9.249]
    4 14 ms 14 ms 14 ms po2.bne-pipe-bdr1.iinet.net.au [203.215.8.30]
    5 14 ms 14 ms 14 ms xe-11-2-0.cr1.bne4.on.ii.net [150.101.33.130]
    6 31 ms 31 ms 31 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
    7 178 ms 178 ms 178 ms te0-1-1-2.br2.lax1.on.ii.net [203.16.213.190]
    8 178 ms 226 ms 178 ms xe-7-0-3.edge2.LosAngeles9.Level3.net [4.53.230.45]
    9 213 ms 212 ms 212 ms vlan90.csw4.LosAngeles1.Level3.net [4.69.144.254]
    10 182 ms 182 ms 183 ms ae-91-91.ebr1.LosAngeles1.Level3.net [4.69.137.13]
    11 183 ms 182 ms 183 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
    12 182 ms 183 ms 183 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    13 183 ms 183 ms 183 ms vl3104.lvssw-2.sonyonline.net [64.37.168.26]
    14 212 ms 183 ms 183 ms lvspsn-liv-gw01.station.sony.com [64.37.174.140]


    At spontaneous while playing the game, I get disconnected. However, it's not the disconnect dialogue box that appears first. I know I'm disconnected when players walk in one direction, through walls and floors and fly-walking. while tanks drift in the air. This can happen within 5mins of playing or over 1 hour. The situation cannot be recreated to demonstrate. The disconnect dialogue box only appears after approx 3-5mins.

    I started a thread before regarding my situation, but unfortunately no fix.(https://forums.station.sony.com/ps2...ng-through-walls-and-ground-or-flying.181192/) So I'm hopeful this is the right direction!
    THE Toad, Jul 13, 2014
    #108

  9. Dave Wright

    Ran this at around 8:20 PM Central Standard Time. (Removed Network Name)

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

    1 1 ms 1 ms <1 ms <REMOVED> [192.168.1.1]
    2 2 ms 2 ms 1 ms 192.168.0.1
    3 * * * Request timed out.
    4 18 ms 15 ms 12 ms host-24-100-53-173.newwavecomm.net [24.100.53.173]
    5 22 ms 15 ms 18 ms host-24-100-53-160.newwavecomm.net [24.100.53.160]
    6 15 ms 14 ms 16 ms host-24-100-53-124.newwavecomm.net [24.100.53.124]
    7 21 ms 21 ms 25 ms kcm-edge-18.inet.qwest.net [72.165.193.65]
    8 33 ms 94 ms 46 ms dap-brdr-03.inet.qwest.net [67.14.2.89]
    9 * * * Request timed out.
    10 91 ms 86 ms 85 ms vl-3502-ve-116.csw1.Dallas1.Level3.net [4.69.146.5]
    11 96 ms 94 ms 88 ms ae-62-62.ebr2.Dallas1.Level3.net [4.69.151.130]
    12 98 ms 88 ms 94 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
    13 150 ms 197 ms 342 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    14 247 ms 195 ms 330 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    15 117 ms 112 ms 121 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    16 122 ms 293 ms 386 ms lp.soe.com [64.37.171.24]

    Trace complete.
    Dave Wright, Jul 13, 2014
    #109

  10. Jaybone

    Connecticut. AT&T Uverse. Looks like AT&T has a couple routers configured to not respond to icmp, and at or just before the handoff to Level3 (looks like it happens in Chicago?), latency doubles.

    3 * * * Request timed out.
    4 24 ms 23 ms 23 ms 32.223.104.37
    5 46 ms 45 ms 51 ms gar13.cgcil.ip.att.net [12.122.132.121]
    6 * * * Request timed out.
    7 92 ms 92 ms 91 ms vl-3506-ve-120.ebr1.Chicago2.Level3.net [4.69.158.134]
    8 93 ms 92 ms 92 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    9 90 ms 90 ms 90 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]
    10 92 ms 91 ms 91 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    11 92 ms 90 ms 90 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    12 91 ms 91 ms 91 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    13 92 ms 93 ms 91 ms lp.soe.com [64.37.171.24]
    Jaybone, Jul 13, 2014
    #110

  11. kmg90

    [IMG]Directly trace from router
    kmg90, Jul 13, 2014
    #111 Last edited by kmg90, Jul 13, 2014

  12. ShadowOfTheMountain

    Hi - From South Dakota 8:45 PM Central Time. Slower responses from Level3.nets.
    ShadowOfTheMountain, Jul 13, 2014
    #112

  13. x7xBillyDaKidx7x

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

    >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 home [192.168.1.254]
    2 31 ms 28 ms 29 ms adsl-70-133-159-254.dsl.ablntx.sbcglobal.net [70
    .133.159.254]
    3 28 ms 28 ms 30 ms dist1-vlan60.ablntx.sbcglobal.net [151.164.166.1
    50]
    4 31 ms 30 ms 30 ms bb2-g8-0-1.ablntx.sbcglobal.net [151.164.166.253
    ]
    5 51 ms 50 ms 50 ms gar26.dlstx.ip.att.net [12.123.16.109]
    6 * * * Request timed out.
    7 83 ms 86 ms 83 ms vl-3504-ve-116.csw2.Dallas1.Level3.net [4.69.146
    .13]
    8 84 ms 86 ms 83 ms ae-72-72.ebr2.Dallas1.Level3.net [4.69.151.142]

    9 85 ms 86 ms 85 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
    10 87 ms 83 ms 115 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    11 165 ms 208 ms 87 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    12 85 ms 86 ms 85 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    13 83 ms 85 ms 85 ms lp.soe.com [64.37.171.24]

    Trace complete.
    x7xBillyDaKidx7x, Jul 13, 2014
    #113

  14. Keiichi25

    Well, mind you... Level 3 controls only part of the internet connections. Providers can and will have issues that they cannot do much about, such as hardware failures, line disconnects... To give an example, the main backbone to the Bay Area was literally severed by some malicious people, blacking out the internet connection for about 2 to 3 days, some businesses that rely on the internet to literally shut down because of a lack of internet.

    You also have to identify where some of the breaks are, as their collection of networks is large.
    Keiichi25, Jul 13, 2014
    #114

  15. Keiichi25

    Actually, telling people the proper information, regardless of whether or not you think it is stupid, is better than misinforming the masses of completely inaccurate information. Further more, not all major networks are 'clusters of servers', but router hardware which doesn't require a 'server' to do the very thing you speak of. What YOU are thinking of, is load balancing with regards to serving data information, such as content providing or web pages to alleviate heavy loads, as originally, most network connections at one point can have an issue delivering content due to distance and bandwidth.

    Hence why there are now data centers to de-centralize some information as noted in the past with MMOs and web site promo experiences, how bogged down a single point tries to deal with large loads and also the emergence of DDOS as a means to attack internet infrastructures which are now more common place.
    • Up x 1
    Keiichi25, Jul 13, 2014
    #115

  16. Cest7

    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.0.1
    2 * * * Request timed out.
    3 15 ms 9 ms 21 ms rd3st-tge0-5-0-6-1.vc.shawcable.net [64.59.148.237]
    4 21 ms 25 ms 20 ms rc2wh-tge0-5-0-6.vc.shawcable.net [66.163.65.130]
    5 19 ms 17 ms 17 ms rd1cs-tge1-1-1.ok.shawcable.net [66.163.77.214]
    6 14 ms 17 ms 15 ms xe-9-3-0.sea22.ip4.tinet.net [77.67.71.173]
    7 18 ms 23 ms 16 ms xe-11-0-1.sea23.ip4.tinet.net [89.149.184.110]
    8 17 ms 13 ms 23 ms as3356.sea21.ip4.tinet.net [199.229.231.186]
    9 45 ms 22 ms 22 ms as3356.sea21.ip4.tinet.net [199.229.231.186]
    10 55 ms 46 ms 45 ms ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150]
    11 163 ms 56 ms 47 ms ae-2-2.ebr2.SanJose5.Level3.net [4.69.148.141]
    12 47 ms 135 ms 172 ms ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201]
    13 61 ms 50 ms 50 ms ae-92-92.csw4.LosAngeles1.Level3.net [4.69.137.30]
    14 48 ms 49 ms 56 ms ae-91-91.ebr1.LosAngeles1.Level3.net [4.69.137.13]
    15 48 ms 48 ms 46 ms ae-91-91.ebr1.LosAngeles1.Level3.net [4.69.137.13]
    16 69 ms 53 ms 53 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    17 54 ms 49 ms 55 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    18 51 ms 47 ms 46 ms lp.soe.com [64.37.171.24]

    Trace complete.

    gets a little slow after level 3, however I've been experiencing massive lag spikes and desyncs over the past few weeks.
    Cest7, Jul 13, 2014
    #116

  17. Sev

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

    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.0.1
    2 63 ms 48 ms 48 ms boid-dsl-gw13.boid.qwest.net [184.99.64.13]
    3 76 ms 47 ms 47 ms boid-agw1.inet.qwest.net [184.99.65.97]
    4 61 ms 88 ms 65 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
    5 98 ms * * ae14.edge2.Seattle1.Level3.net [4.68.62.189]
    6 112 ms 106 ms 108 ms ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150]

    7 167 ms 166 ms 143 ms ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49]
    8 111 ms 109 ms 106 ms ae-2-2.ebr2.SanJose5.Level3.net [4.69.148.141]
    9 113 ms 110 ms 114 ms ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201
    ]
    10 107 ms 106 ms 108 ms ae-82-82.csw3.LosAngeles1.Level3.net [4.69.137.2
    6]
    11 108 ms 110 ms 125 ms ae-81-81.ebr1.LosAngeles1.Level3.net [4.69.137.9
    ]
    12 127 ms 119 ms 122 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

    13 125 ms 107 ms 107 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    14 112 ms 110 ms 114 ms lp.soe.com [64.37.171.24]

    Trace complete.
    Sev, Jul 13, 2014
    #117

  18. KaossKing

    heres another one from UK taking first thing in the morning. pretty clear where the problem lies

    Microsoft Windows
    (c) 2013 Microsoft Corporation. All rights reserved.

    D:\Windows\System32>tracert lp.soe.com

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

    1 10 ms 11 ms 4 ms SkyRouter.Home
    2 * * * Request timed out.
    3 25 ms 24 ms 21 ms
    4 129 ms 137 ms 115 ms ae51.edge6.London1.Level3.net [212.113.9.53]
    5 226 ms 222 ms 190 ms vl-3615-ve-239.csw2.London1.Level3.net [4.69.166
    .90]
    6 186 ms 182 ms 192 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]

    7 153 ms 153 ms 153 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

    8 154 ms 155 ms 155 ms ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
    9 154 ms 154 ms 153 ms ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]

    10 155 ms 153 ms 179 ms ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
    11 153 ms 184 ms 153 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
    12 155 ms 154 ms 154 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    13 155 ms 154 ms 155 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    14 155 ms 184 ms 156 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    15 186 ms 181 ms 192 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    16 174 ms 177 ms 169 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    17 203 ms 186 ms 185 ms lp.soe.com [64.37.171.24]

    Trace complete.

    D:\Windows\System32>
    KaossKing, Jul 14, 2014
    #118

  19. Theperp

    Trace from the netherlands to ip.soe.com




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

    1 3 ms 1 ms 1 ms 192.168.0.1
    2 2 ms 2 ms 1 ms 192.168.178.1
    3 14 ms 9 ms 8 ms 10.241.60.1
    4 14 ms 9 ms 18 ms tb-rc0001-cr101-xe-0-1-4-0.core.as9143.net [213.
    51.186.0]
    5 28 ms 18 ms 11 ms asd-tr0042-cr101-ae5-0.core.as9143.net [213.51.1
    58.18]
    6 26 ms 28 ms 18 ms te4-6.ccr01.ams09.atlas.cogentco.com [149.14.34.
    173]
    7 20 ms 17 ms 11 ms te0-1-0-10.ccr41.ams03.atlas.cogentco.com [154.5
    4.63.177]
    8 22 ms 28 ms 21 ms be2182.ccr21.lpl01.atlas.cogentco.com [154.54.77
    .246]
    9 99 ms 98 ms 98 ms be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44
    .137]
    10 103 ms 106 ms 109 ms be2090.ccr21.yyz02.atlas.cogentco.com [154.54.30
    .205]
    11 102 ms 104 ms 99 ms level3.yyz02.atlas.cogentco.com [154.54.11.210]

    12 120 ms * * ae-23-23.bar2.Toronto1.Level3.net [4.69.200.237]

    13 129 ms 126 ms 101 ms ae-0-11.bar1.Toronto1.Level3.net [4.69.151.241]

    14 157 ms 155 ms 157 ms ae-9-9.ebr1.Chicago1.Level3.net [4.69.151.110]
    15 156 ms 155 ms 154 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
    16 158 ms 156 ms 155 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    17 156 ms 158 ms 154 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    18 159 ms 154 ms 155 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    19 156 ms 154 ms 178 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    20 158 ms 157 ms 154 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    21 158 ms 156 ms 157 ms lp.soe.com [64.37.171.24]

    Trace complete.


    And to Miller:

    Tracing route to amspsn-liv-gw02.planetside2.com [69.174.194.166]
    over a maximum of 30 hops:

    1 3 ms 1 ms 1 ms 192.168.0.1
    2 2 ms 1 ms 1 ms 192.168.178.1
    3 9 ms 18 ms 9 ms 10.241.60.1
    4 10 ms 10 ms 9 ms tb-rc0001-cr101-xe-0-1-4-0.core.as9143.net [213.
    51.186.0]
    5 14 ms 12 ms 12 ms asd-tr0042-cr101-ae5-0.core.as9143.net [213.51.1
    58.18]
    6 12 ms 12 ms 11 ms ve4.bg3.ama.as16243.net [195.69.145.222]
    7 13 ms 22 ms 21 ms ve85.bg3.am1.as16243.net [87.249.109.2]
    8 14 ms 21 ms 12 ms po6-1500.bg1.am1.eu.equinix.net [77.222.66.82]
    9 13 ms 11 ms 12 ms po7.bg1.am3.eu.equinix.net [94.103.16.86]
    10 12 ms 341 ms 13 ms sony.customer.am3.eu.equinix.net [5.175.82.90]
    11 15 ms 15 ms 11 ms amspsn-liv-gw02.planetside2.com [69.174.194.166]


    Trace complete.
    Theperp, Jul 14, 2014
    #119

  20. Syncaidius

    Heres one from the UK to lp.soe.com

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 34 ms 33 ms 34 ms host-92-13-48-1.as43234.net [92.13.48.1]
    3 35 ms 34 ms 72 ms host-92-31-244-5.as13285.net [92.31.244.5]
    4 34 ms 34 ms 35 ms host-92-31-244-24.as13285.net [92.31.244.24]
    5 42 ms 41 ms 41 ms host-78-144-8-47.as13285.net [78.144.8.47]
    6 41 ms 40 ms 40 ms host-78-144-10-230.as13285.net [78.144.10.230]
    7 42 ms 42 ms 42 ms ae53.edge4.London2.Level3.net [212.187.192.113]

    8 187 ms 187 ms 188 ms vl-3202-ve-130.ebr2.London2.Level3.net [4.69.202
    .181]
    9 191 ms 191 ms 191 ms ae-42-42.ebr1.Paris1.Level3.net [4.69.159.86]
    10 186 ms 186 ms 197 ms ae-61-61.csw1.Paris1.Level3.net [4.69.161.78]
    11 205 ms 187 ms 187 ms ae-62-62.ebr2.Paris1.Level3.net [4.69.161.93]
    12 189 ms 189 ms 232 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5
    0]
    13 186 ms 191 ms 187 ms ae-47-47.ebr2.Washington12.Level3.net [4.69.202.
    58]
    14 187 ms 186 ms 185 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    15 188 ms 188 ms 188 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

    16 188 ms 188 ms 188 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    17 191 ms 191 ms 192 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    18 192 ms 221 ms 191 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    19 187 ms 186 ms 186 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    20 185 ms 184 ms 184 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    21 183 ms 184 ms 184 ms lp.soe.com [64.37.171.24]
    Syncaidius, Jul 14, 2014
    #120
Page 6 of 23
Thread Status:
Not open for further replies.