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 1 of 23

  1. d_carey Developer

    Our Operations team is following up on the issues with Level3 but they could use some information. Please post your location and what issues you are experiencing and Ops will follow up with any updates.

    Thanks.
    • Up x 5
    d_carey, Jul 12, 2014
    #1

  2. Jonas Chupp

    Is level 3 a code-name with which you are communicating to a select crowd of people through this post to prevent disclosure of a secret operation? Or is it just something dumb that I'm an idiot for not knowing what it is?
    • Up x 13
    Jonas Chupp, Jul 12, 2014
    #2

  3. Hypersot

    Level3? ...
    Hypersot, Jul 12, 2014
    #3

  4. GlueHead

    • Up x 2
    GlueHead, Jul 12, 2014
    #4 Last edited by GlueHead, Jul 12, 2014

  5. agrueeatedu

    Here's a traceroute from about a month ago. Issues off and on during peak use times.

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

    1 <1 ms <1 ms <1 ms modem.Home [192.168.0.1]
    2 23 ms 22 ms 23 ms mpls-dsl-gw58.mpls.qwest.net [207.225.140.58]
    3 23 ms 23 ms 23 ms mpls-agw1.inet.qwest.net [75.168.229.201]
    4 33 ms 33 ms 34 ms chp-brdr-03.inet.qwest.net [67.14.8.194]
    5 55 ms 53 ms 52 ms 63.146.27.18
    6 319 ms 308 ms 318 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
    7 217 ms 208 ms 198 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    8 294 ms 284 ms 284 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]
    9 222 ms 211 ms 218 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    10 323 ms 309 ms 312 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    11 159 ms 163 ms 164 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    12 217 ms 220 ms 210 ms lp.soe.com [64.37.171.24]

    Trace complete.
    My ISP is CenturyLink, and I play on Connery.
    • Up x 1
    agrueeatedu, Jul 12, 2014
    #5

  6. DorianOmega

    Level3 is apparently a server base that people have their internet connections ping through when connecting to SOEs servers and has been know to cause erratic connection issues in the past.
    • Up x 2
    DorianOmega, Jul 12, 2014
    #6 Last edited by DorianOmega, Jul 12, 2014

  7. LocoCoyote

    just did a tracert, seemed OK?

    Tracing route to lp.soe.com [64.37.171.24]

    14 ms 15 ms 15 ms he-3-9-0-0-cr01.denver.co.ibone.comcast.net [68.86.92.21]
    12 ms 32 ms 13 ms ae14.edge3.Denver1.Level3.net [4.68.127.129]
    41 ms 40 ms 42 ms vlan51.ebr1.Denver1.Level3.net [4.69.147.94]
    44 ms 51 ms 41 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    41 ms 40 ms 40 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    41 ms 42 ms 45 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    44 ms 61 ms 42 ms lp.soe.com [64.37.171.24]
    LocoCoyote, Jul 12, 2014
    #7

  8. Jerexise

    Everyday for little over 2 weeks now from around 5pm to 12am my ping goes from 68ms avg to 200ms avg during that time period. Will post a traceroute tonight during that time period.
    • Up x 1
    Jerexise, Jul 12, 2014
    #8

  9. Jonas Chupp

    I was sort of hoping level 3 had something to do with an ancient alien race living among us. Guess not.
    • Up x 4
    Jonas Chupp, Jul 12, 2014
    #9

  10. SpionBref

    This is Ceres right now (I live close to Amsterdam) --

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

    1 1 ms 4 ms 1 ms 192.168.1.254
    2 * 22 ms 23 ms 195-240-127-254.ip.telfort.nl [195.240.127.254]

    3 31 ms 159 ms 146 ms ve4.bg3.ama.as16243.net [195.69.145.222]
    4 89 ms 49 ms 125 ms ve85.bg3.am1.as16243.net [87.249.109.2]
    5 202 ms 159 ms 524 ms po6-1500.bg1.am1.eu.equinix.net [77.222.66.82]
    6 381 ms 429 ms 391 ms po7.bg1.am3.eu.equinix.net [94.103.16.86]
    7 297 ms 173 ms 252 ms sony.customer.am3.eu.equinix.net [5.175.82.90]
    8 96 ms 159 ms 107 ms amspsn-liv-gw04.planetside2.com [69.174.194.168]
    SpionBref, Jul 12, 2014
    #10

  11. Wishbringer75

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

    1 1 ms 1 ms <1 ms gw-n1-aepv-d6.ias.bredband.telia.com [78.72.85.65]
    2 2 ms 2 ms 3 ms s-b6-link.telia.net [62.115.138.59]
    3 * 27 ms 27 ms level3-ic-155475-s-b2.c.telia.net [213.248.99.134]
    4 185 ms 185 ms 185 ms vl-3508-ve-114.ebr1.Stockholm2.Level3.net [4.69.158.254]
    5 179 ms 179 ms 189 ms ae-44-44.ebr1.Dusseldorf1.Level3.net [4.69.201.242]
    6 185 ms 187 ms 185 ms ae-45-45.ebr3.Frankfurt1.Level3.net [4.69.143.166]
    7 180 ms 180 ms 180 ms ae-93-93.csw4.Frankfurt1.Level3.net [4.69.163.14]
    8 184 ms 184 ms 184 ms ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13]
    9 185 ms 185 ms 186 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
    10 184 ms 184 ms 184 ms ae-42-42.ebr2.Washington1.Level3.net [4.69.137.54]
    11 178 ms 178 ms 179 ms ae-46-46.ebr2.Washington12.Level3.net [4.69.202.54]
    12 180 ms 180 ms 180 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    13 183 ms 183 ms 183 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
    14 178 ms 178 ms 178 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    15 179 ms 180 ms 179 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]
    16 180 ms 180 ms 180 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    17 183 ms 205 ms 183 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    18 179 ms 179 ms 179 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    19 179 ms 179 ms 179 ms lp.soe.com [64.37.171.24]

    Trace complete.
    Wishbringer75, Jul 12, 2014
    #11

  12. FeralCarr

    Here is my trace

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

    1 10 ms 10 ms 12 ms 10.192.128.1
    2 12 ms 11 ms 13 ms 72-31-193-92.net.bhntampa.com [72.31.193.92]
    3 13 ms 13 ms 14 ms ten0-10-0-2.orld71-car1.bhn.net [97.69.194.80]
    4 16 ms 13 ms 14 ms 72-31-188-172.net.bhntampa.com [72.31.188.172]
    5 * 24 ms 22 ms 4.68.70.153
    6 77 ms 76 ms 75 ms ae-8-8.ebr1.Atlanta2.Level3.net [4.69.137.150]
    7 * * * Request timed out.
    8 75 ms 75 ms 73 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
    9 74 ms 74 ms 79 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]
    10 74 ms 74 ms 75 ms ae-82-82.ebr2.Dallas1.Level3.net [4.69.151.154]
    11 75 ms 74 ms 75 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
    12 75 ms 74 ms 122 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    13 75 ms 73 ms 76 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    14 79 ms 75 ms 75 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    15 90 ms 74 ms 85 ms lp.soe.com [64.37.171.24]
    FeralCarr, Jul 12, 2014
    #12

  13. jared12100

    My trace

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

    1 2 ms 1 ms 3 ms 192.168.2.1
    2 7 ms 8 ms 6 ms 10.255.252.1
    3 7 ms 7 ms 6 ms BE7-84.cr01.hlfx.ns.aliant.net [142.176.53.50]
    4 56 ms 6 ms 8 ms be4.cr01.mctn.nb.aliant.net [142.166.129.69]
    5 7 ms 11 ms 7 ms ae3.cr02.mctn.nb.aliant.net [142.166.185.138]
    6 23 ms 22 ms 23 ms et-4-1-0.bx01.mtrl.pq.aliant.net [207.231.227.12
    6]
    7 28 ms 27 ms 31 ms et-10-1-0.bx01.toro.on.aliant.net [207.231.227.1
    21]
    8 29 ms 27 ms 27 ms 38.88.240.53
    9 28 ms 27 ms 28 ms be2373.ccr21.yyz02.atlas.cogentco.com [154.54.46
    .33]
    10 25 ms 28 ms 27 ms level3.yyz02.atlas.cogentco.com [154.54.11.210]

    11 * 26 ms 29 ms ae-13-13.bar1.Toronto1.Level3.net [4.69.200.233]

    12 87 ms 89 ms 91 ms ae-9-9.ebr1.Chicago1.Level3.net [4.69.151.110]
    13 87 ms 84 ms 87 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
    14 88 ms 133 ms 85 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    15 85 ms 87 ms 91 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    16 84 ms 88 ms 86 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    17 86 ms 87 ms 92 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    18 84 ms 83 ms 83 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    19 89 ms 88 ms 88 ms lp.soe.com [64.37.171.24]

    Trace complete.
    jared12100, Jul 12, 2014
    #13

  14. jared12100


    Also the problem i'm having (not sure if its related or not) is when i hit play the game starts to load but after about 2 seconds stops and i have to hit play again. Then it stops. I cant load the game but all files are verified to be working.
    jared12100, Jul 12, 2014
    #14

  15. AlainBadiou

    I live in Iowa.

    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 18 ms 7 ms 8 ms 10.141.78.1
    3 12 ms 11 ms 10 ms 172.30.72.81
    4 14 ms 10 ms 12 ms 172.30.11.89
    5 16 ms 15 ms 19 ms 12.249.240.33
    6 15 ms 16 ms 18 ms cr2.cgcil.ip.att.net [12.122.132.250]
    7 17 ms 21 ms 18 ms gar13.cgcil.ip.att.net [12.122.132.121]
    8 * * 37 ms 192.205.37.150
    9 85 ms 81 ms 80 ms vl-3507-ve-121.ebr1.Chicago2.Level3.net [4.69.15
    8.138]
    10 79 ms 78 ms 78 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    11 91 ms 80 ms 85 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    12 79 ms 79 ms 83 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    13 115 ms 81 ms 95 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    14 82 ms 79 ms 79 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    15 80 ms 81 ms 81 ms lp.soe.com [64.37.171.24]

    Trace complete.

    At the moment, it's not too bad. During peak hours, I've been suffering from latency around 150-200 and the main culprit often seems to be 192.205.37.150.
    AlainBadiou, Jul 12, 2014
    #15

  16. Klaus Myrseth

    Here is from norway, I hate level3 as its always crap whatever I run through there.

    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.1.1
    2 6 ms 12 ms 6 ms 1.81-167-197.customer.lyse.net [81.167.197.1]
    3 1 ms 1 ms 1 ms 153.81-167-208.customer.lyse.net [81.167.208.153]
    4 5 ms 5 ms 6 ms 244.81-167-208.customer.lyse.net [81.167.208.244]
    5 3 ms 6 ms 6 ms 153.81-166-123.customer.lyse.net [81.166.123.153]
    6 2 ms 3 ms 2 ms xe-8-0-0.bar1.Oslo1.Level3.net [212.162.27.61]
    7 11 ms 15 ms 11 ms ae-9-5.bar1.Copenhagen1.Level3.net [4.69.201.74]
    8 173 ms 173 ms 173 ms ae-7-7.ebr1.Dusseldorf1.Level3.net [4.69.142.170]
    9 172 ms 172 ms 172 ms ae-46-46.ebr3.Frankfurt1.Level3.net [4.69.143.170]
    10 175 ms 174 ms 178 ms ae-63-63.csw1.Frankfurt1.Level3.net [4.69.163.2]
    11 176 ms 200 ms 192 ms ae-61-61.ebr1.Frankfurt1.Level3.net [4.69.140.1]
    12 177 ms 198 ms 191 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
    13 173 ms 173 ms 173 ms ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
    14 173 ms 173 ms 173 ms ae-45-45.ebr2.Washington12.Level3.net [4.69.143.222]
    15 192 ms 177 ms 177 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    16 178 ms 179 ms 189 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
    17 179 ms 178 ms 178 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    18 177 ms 177 ms 179 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]
    19 197 ms 177 ms 187 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    20 198 ms 176 ms 178 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    21 175 ms 175 ms 175 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    22 175 ms 174 ms 175 ms lp.soe.com [64.37.171.24]

    Trace complete.
    Klaus Myrseth, Jul 12, 2014
    #16

  17. doombro

    Well, since everyone else is doing it

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

    1 33 ms 26 ms 15 ms cpe-107-015-064-001.nc.res.rr.com [107.15.64.1]
    2 12 ms 11 ms 11 ms 66.26.45.169
    3 14 ms 26 ms 14 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0]
    4 18 ms 22 ms 23 ms 107.14.19.20
    5 27 ms 19 ms 30 ms 107.14.17.179
    6 19 ms 57 ms 26 ms 107.14.19.160
    7 19 ms 23 ms 57 ms ge-7-1-6.pr0.chi10.tbone.rr.com [66.109.9.74]
    8 87 ms 76 ms 78 ms vlan80.csw3.Washington1.Level3.net [4.69.149.190]
    9 76 ms 79 ms 77 ms ae-82-82.ebr2.Washington1.Level3.net [4.69.134.153]
    10 86 ms 76 ms 75 ms ae-46-46.ebr2.Washington12.Level3.net [4.69.202.54]
    11 79 ms 78 ms 78 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    12 87 ms 78 ms 75 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
    13 86 ms 81 ms 76 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
    14 78 ms 81 ms 78 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]
    15 77 ms 86 ms 77 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    16 77 ms 146 ms 124 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    17 75 ms 78 ms 88 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    18 81 ms 78 ms 79 ms lp.soe.com [64.37.171.24]

    Trace complete
    doombro, Jul 12, 2014
    #17

  18. Utrooperx

    I've have had similar issues with Level3.net...I contacted them by posting on their Facebook page and they simply referred me to my local ISP...even after I posted the tracert and pingpath showing the problem was a Level3 server, not Verizon.

    Despite two follow up attempts, they have simply ignored me...

    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 Wireless_Broadband_Router.home [192.168.1.1]
    2 7 ms 6 ms 5 ms L100.TAMPFL-VFTTP-67.verizon-gni.net [96.228.225
    .1]
    3 12 ms 11 ms 11 ms G0-5-4-2.TAMPFL-LCR-22.verizon-gni.net [130.81.1
    10.210]
    4 10 ms 9 ms 9 ms ae8-0.TPA01-BB-RTR2.verizon-gni.net [130.81.162.
    128]
    5 25 ms 26 ms 26 ms 0.xe-7-3-0.BR3.ATL4.ALTER.NET [152.63.5.129]
    6 42 ms 41 ms 38 ms ae17.edge5.Atlanta2.level3.net [4.68.62.37]
    7 * * * Request timed out.
    8 98 ms 95 ms 97 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
    9 97 ms 97 ms 97 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]
    10 97 ms 97 ms 100 ms ae-82-82.ebr2.Dallas1.Level3.net [4.69.151.154]
    11 100 ms 96 ms 95 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
    12 99 ms 97 ms 100 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    13 97 ms 96 ms 146 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    14 98 ms 97 ms 101 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    15 99 ms 97 ms 99 ms vl3104.lvssw-2.sonyonline.net [64.37.168.26]
    16 94 ms 95 ms 95 ms lvspsn-liv-gw01.station.sony.com [64.37.174.140]

    Trace complete.

    Tracing route to lvspsn-liv-gw01.station.sony.com [64.37.174.140]
    over a maximum of 30 hops:
    0 Keith-PC.home [192.168.1.2]
    1 Wireless_Broadband_Router.home [192.168.1.1]
    2 L100.TAMPFL-VFTTP-67.verizon-gni.net [96.228.225.1]
    3 G0-5-4-2.TAMPFL-LCR-22.verizon-gni.net [130.81.110.210]
    4 ae8-0.TPA01-BB-RTR2.verizon-gni.net [130.81.162.128]
    5 0.xe-7-3-0.BR3.ATL4.ALTER.NET [152.63.5.129]
    6 ae17.edge5.Atlanta2.level3.net [4.68.62.37]
    7 * * *
    Computing statistics for 150 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Keith-PC.home [192.168.1.2]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [19
    2.168.1.1]
    0/ 100 = 0% |
    2 9ms 0/ 100 = 0% 0/ 100 = 0% L100.TAMPFL-VFTTP-67.verizon-gni.n
    et [96.228.225.1]
    0/ 100 = 0% |
    3 10ms 0/ 100 = 0% 0/ 100 = 0% G0-5-4-2.TAMPFL-LCR-22.verizon-gni
    .net [130.81.110.210]
    0/ 100 = 0% |
    4 15ms 0/ 100 = 0% 0/ 100 = 0% ae8-0.TPA01-BB-RTR2.verizon-gni.ne
    t [130.81.162.128]
    0/ 100 = 0% |
    5 26ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-7-3-0.BR3.ATL4.ALTER.NET [152
    .63.5.129]
    0/ 100 = 0% |
    6 42ms 0/ 100 = 0% 0/ 100 = 0% ae17.edge5.Atlanta2.level3.net [4.
    68.62.37]
    Trace complete.

    Notice how my latency doubles between hop 6 and hop 8? Pretty sure there is a issue with the equipment at hop 7...and its on the Level3.net equipment...the pathping won't even go beyond that point.
    Utrooperx, Jul 12, 2014
    #18

  19. RailFury

    My typical trace originating from the Mediacom ISP out of Cedar Rapids, IA. This occurs on weeknights between 8-11pm CST (sometimes longer, rarely shorter). I've been running this trace every 30 minutes for that last month. Here is a typical result during these peak hours.

    Tue 07-08-2014@23-00-00.38
    Tracing route to 199.108.194.41 over a maximum of 30 hops

    1 8 ms 6 ms 7 ms 10.168.32.1
    2 8 ms 7 ms 8 ms 10.168.32.1
    3 8 ms 9 ms 9 ms 172.30.72.129
    4 9 ms 9 ms 9 ms 172.30.11.89
    5 14 ms 14 ms 18 ms 12.249.81.45
    6 18 ms 19 ms 19 ms cr2.cgcil.ip.att.net [12.122.132.182]
    7 16 ms 19 ms 17 ms gar13.cgcil.ip.att.net [12.122.132.121]
    8 * * * Request timed out.
    9 127 ms 127 ms 127 ms vl-3607-ve-231.ebr2.Chicago2.Level3.net [4.69.158.154]
    10 127 ms 126 ms 125 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.145]
    11 125 ms 125 ms 128 ms ae-46-46.ebr2.Washington1.Level3.net [4.69.202.53]
    12 122 ms 126 ms 120 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.146]
    13 126 ms 119 ms 119 ms ae-4-90.edge1.Washington4.Level3.net [4.69.149.207]
    14 126 ms 124 ms 122 ms SONY-ONLINE.edge1.Washington4.Level3.net [4.53.112.6]


    And here is just a little later after peak times have ended...

    Wed 07-09-2014@ 0-00-00.45

    Tracing route to 199.108.194.41 over a maximum of 30 hops

    1 9 ms 8 ms 9 ms 10.168.32.1
    2 7 ms 8 ms 7 ms 10.168.32.1
    3 8 ms 8 ms 7 ms 172.30.72.129
    4 9 ms 8 ms 8 ms 172.30.11.89
    5 15 ms 14 ms 18 ms 12.249.81.45
    6 18 ms 15 ms 15 ms cr2.cgcil.ip.att.net [12.122.132.182]
    7 25 ms 18 ms 14 ms gar13.cgcil.ip.att.net [12.122.132.121]
    8 * * * Request timed out.
    9 50 ms 47 ms 49 ms vl-3607-ve-231.ebr2.Chicago2.Level3.net [4.69.158.154]
    10 52 ms 50 ms 52 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.145]
    11 49 ms 52 ms 52 ms ae-46-46.ebr2.Washington1.Level3.net [4.69.202.53]
    12 53 ms 49 ms 49 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]
    13 52 ms 54 ms 55 ms ae-4-90.edge1.Washington4.Level3.net [4.69.149.207]
    14 50 ms 50 ms 51 ms SONY-ONLINE.edge1.Washington4.Level3.net [4.53.112.6]
    • Up x 1
    RailFury, Jul 12, 2014
    #19 Last edited by RailFury, Jul 12, 2014

  20. Grish

    German Telekom tracepath (UDP):
    1: 192.168.178.1 (192.168.178.1) 0.663ms
    2: 217.0.116.15 (217.0.116.15) 19.039ms asymm 3
    3: 217.0.65.6 (217.0.65.6) 20.709ms
    4: l-eb2-i.L.DE.NET.DTAG.DE (62.154.89.46) 21.362ms asymm 6
    5: 217.243.216.202 (217.243.216.202) 52.384ms asymm 6
    6: vlan80.csw3.Frankfurt1.Level3.net (4.69.154.190) 124.252ms asymm 11
    7: ae-83-83.ebr3.Frankfurt1.Level3.net (4.69.163.9) 122.927ms asymm 11
    8: ae-46-46.ebr1.Dusseldorf1.Level3.net (4.69.143.169) 119.223ms asymm 11
    9: ae-21-21.ebr2.Dusseldorf1.Level3.net (4.69.143.182) 126.587ms asymm 11
    10: ae-47-47.ebr1.Amsterdam1.Level3.net (4.69.143.205) 121.726ms asymm 11
    11: ae-59-114.csw1.Amsterdam1.Level3.net (4.69.153.198) 121.748ms asymm 10
    12: 4.69.162.162 (4.69.162.162) 125.926ms asymm 9
    13: SONY-ONLINE.edge3.Amsterdam1.Level3.net (212.72.33.26) 128.129ms asymm 10
    14: SONY-ONLINE.edge3.Amsterdam1.Level3.net (212.72.33.26) 129.296ms !H
    Resume: pmtu 149

    Network hop 5 and 6 are often overloaded at peak times for "home internet access".

    The same IX over a Telekom company connect:
    4: l-eb2-i.L.DE.NET.DTAG.DE (62.154.89.46) 8.700ms asymm 6
    5: 217.243.216.202 (217.243.216.202) 29.349ms asymm 6
    6: vlan70.csw2.Frankfurt1.Level3.net (4.69.154.126) 24.321ms asymm 10
    7: ae-73-73.ebr3.Frankfurt1.Level3.net (4.69.163.5) 24.182ms asymm 10
    8: ae-48-48.ebr1.Dusseldorf1.Level3.net (4.69.143.177) 36.372ms asymm 10
    9: ae-23-23.ebr2.Dusseldorf1.Level3.net (4.69.143.190) 24.196ms asymm 10
    10: ae-45-45.ebr1.Amsterdam1.Level3.net (4.69.143.197) 24.374ms
    11: ae-59-114.csw1.Amsterdam1.Level3.net (4.69.153.198) 24.647ms asymm 9
    12: 4.69.162.166 (4.69.162.166) 25.454ms asymm 8
    13: SONY-ONLINE.edge3.Amsterdam1.Level3.net (212.72.33.26) 25.648ms asymm 9
    14: SONY-ONLINE.edge3.Amsterdam1.Level3.net (212.72.33.26) 25.915ms !H
    Grish, Jul 12, 2014
    #20
Page 1 of 23
Thread Status:
Not open for further replies.