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

  1. DLL2

    A other horrible week end because 50% or Kobalt are German and German use level 3 for connect to soe.
    Plz buff level3.
    DLL2, Sep 7, 2014
    #241

  2. Magicool

    Routenverfolgung zu lp.soe.com [64.37.171.24]
    ber maximal 30 Abschnitte:
    0 Christian-PC.fritz.box [192.168.178.21]
    1 fritz.box [192.168.178.1]
    2 rdsl-krlh-de80.nw.mediaways.net [213.20.56.142]
    3 xmws-krlh-de01-chan-20.nw.mediaways.net [62.53.220.129]
    4 rmws-krlh-de01-gigaet-0-0-0.nw.mediaways.net [62.53.222.46]
    5 rmwc-stgt-de01-so-2-0-0.nw.mediaways.net [62.53.1.46]
    6 rmwc-brln-de02-xe-0-0-3.nw.mediaways.net [62.53.1.43]
    7 rmwc-brln-de01-chan-5-0.nw.mediaways.net [62.53.1.112]
    8 So3-3-0-0-grtparix1.red.telefonica-wholesale.net [84.16.10.213]
    9 Xe6-0-8-0-grtwaseq2.red.telefonica-wholesale.net [94.142.116.205]
    10 Xe-1-0-2-0-grtdaleq4.red.telefonica-wholesale.net [94.142.120.89]
    11 xe-10-1-1.edge5.Dallas3.Level3.net [4.71.122.5]
    12 * * *
    Berechnung der Statistiken dauert ca. 275 Sekunden...
    Quelle zum Abs. Knoten/Verbindung
    Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
    0 Christian-PC.fritz.box [192.168.178.21]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
    0/ 100 = 0% |
    2 19ms 0/ 100 = 0% 0/ 100 = 0% rdsl-krlh-de80.nw.mediaways.net [213.20.56.142]
    0/ 100 = 0% |
    3 33ms 0/ 100 = 0% 0/ 100 = 0% xmws-krlh-de01-chan-20.nw.mediaways.net [62.53.220.129]
    0/ 100 = 0% |
    4 32ms 0/ 100 = 0% 0/ 100 = 0% rmws-krlh-de01-gigaet-0-0-0.nw.mediaways.net [62.53.222.46]
    0/ 100 = 0% |
    5 37ms 0/ 100 = 0% 0/ 100 = 0% rmwc-stgt-de01-so-2-0-0.nw.mediaways.net [62.53.1.46]
    0/ 100 = 0% |
    6 50ms 0/ 100 = 0% 0/ 100 = 0% rmwc-brln-de02-xe-0-0-3.nw.mediaways.net [62.53.1.43]
    0/ 100 = 0% |
    7 50ms 0/ 100 = 0% 0/ 100 = 0% rmwc-brln-de01-chan-5-0.nw.mediaways.net [62.53.1.112]
    0/ 100 = 0% |
    8 65ms 0/ 100 = 0% 0/ 100 = 0% So3-3-0-0-grtparix1.red.telefonica-wholesale.net [84.16.10.213]
    0/ 100 = 0% |
    9 154ms 0/ 100 = 0% 0/ 100 = 0% Xe6-0-8-0-grtwaseq2.red.telefonica-wholesale.net [94.142.116.205]
    0/ 100 = 0% |
    10 187ms 0/ 100 = 0% 0/ 100 = 0% Xe-1-0-2-0-grtdaleq4.red.telefonica-wholesale.net [94.142.120.89]
    100/ 100 =100% |
    11 --- 100/ 100 =100% 0/ 100 = 0% xe-10-1-1.edge5.Dallas3.Level3.net [4.71.122.5]

    Ablaufverfolgung beendet.

    Routenverfolgung zu lp.soe.com [64.37.171.24] ber maximal 30 Abschnitte:

    1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
    2 20 ms 21 ms 21 ms rdsl-krlh-de80.nw.mediaways.net [213.20.56.142]
    3 20 ms 20 ms 19 ms xmws-krlh-de01-chan-20.nw.mediaways.net [62.53.220.129]
    4 19 ms 19 ms 19 ms rmws-krlh-de01-gigaet-0-0-0.nw.mediaways.net [62.53.222.46]
    5 22 ms 21 ms 22 ms rmwc-stgt-de01-so-2-0-0.nw.mediaways.net [62.53.1.46]
    6 38 ms 35 ms 35 ms rmwc-brln-de02-xe-0-0-2.nw.mediaways.net [62.53.1.41]
    7 83 ms 118 ms 34 ms rmwc-brln-de01-chan-5-0.nw.mediaways.net [62.53.1.112]
    8 54 ms 55 ms 55 ms So3-3-0-0-grtparix1.red.telefonica-wholesale.net [84.16.10.213]
    9 138 ms 137 ms 132 ms Xe5-0-3-0-grtwaseq3.red.telefonica-wholesale.net [94.142.123.193]
    10 259 ms 190 ms 178 ms Xe2-1-6-0-grtdaleq4.red.telefonica-wholesale.net [94.142.127.97]
    11 248 ms 257 ms 260 ms xe-10-1-1.edge5.Dallas3.Level3.net [4.71.122.5]
    12 * * * Zeitberschreitung der Anforderung (Connection timeout).
    13 * * * Zeitberschreitung der Anforderung (Connection timeout).
    14 * * * Zeitberschreitung der Anforderung (Connection timeout).
    15 206 ms 205 ms 209 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    16 261 ms 288 ms 226 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    17 209 ms 210 ms 212 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    18 208 ms 211 ms 211 ms lp.soe.com [64.37.171.24]
    Magicool, Sep 7, 2014
    #242

  3. Coraxcor

    hm, Leute, ich glaub wenn ihr auf den europäischen Servern spielt solltet ihr für die Routenverfolgung die IP von den Servern nehmen und nicht die von denen in Amerika. Hab weiter vorne hier im Thread folgende IP dazu gefunden:

    amspsn-liv-gw02.planetside2.com [69.174.194.166]

    Bei mir also:

    Routenverfolgung zu amspsn-liv-gw02.planetside2.com [69.174.194.166] über maxima
    l 30 Abschnitte:
    1 <1 ms <1 ms <1 ms 192.168.2.1
    2 17 ms 16 ms 16 ms 217.0.119.47
    3 18 ms 19 ms 18 ms 217.0.75.174
    4 17 ms 18 ms 18 ms 217.239.42.233
    5 18 ms 18 ms 18 ms 80.156.161.190
    6 * * * Zeitüberschreitung der Anforderung.
    7 21 ms 21 ms 21 ms ae-46-46.ebr1.Amsterdam1.Level3.net [4.69.143.201]
    8 * * * Zeitüberschreitung der Anforderung.
    9 22 ms 22 ms 23 ms ae-129-3515.edge6.Amsterdam1.Level3.net [4.69.162.234]
    10 22 ms 26 ms 24 ms SONY-ONLINE.edge6.Amsterdam1.Level3.net [212.72.46.190]
    11 21 ms 21 ms 21 ms amspsn-liv-gw02.planetside2.com [69.174.194.166]
    Ablaufverfolgung beendet.

    Ingame dann mit 60 ms angezeigt.

    --------------------------------------

    Clarified that the IP for european servers is the one above in Amsterdam, and not somewhere in America.
    Coraxcor, Sep 8, 2014
    #243

  4. HyperMatrix

    Still hitting anywhere between 120ms-150ms on average on the west coast...even though I'm on the west coast and used to get 65ms. I cancelled my sub and won't spend another dime in this game until the issue is resolved. It makes no sense that I get lower ping to east coast servers, which are farther away.

    Why make this thread to begin with, SOE? It has resulted in nothing. No fix. And not even any communication regarding the issue. It's been like this for about 4 months now.
    HyperMatrix, Sep 8, 2014
    #244

  5. Komotz

    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 1 ms <1 ms <1 ms mywimax [192.168.15.1]
    3 * * * Request timed out.
    4 65 ms 74 ms 79 ms 10.41.229.193
    5 65 ms 59 ms 64 ms 71.22.8.161
    6 65 ms 59 ms 79 ms 71.22.8.253
    7 130 ms 68 ms 54 ms xe-10-3-0.bar1.SanFrancisco1.Level3.net [4.53.13
    2.13]
    8 81 ms 79 ms 79 ms ae-1-4.ebr1.SanJose5.Level3.net [4.69.140.150]
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 80 ms 79 ms 204 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

    14 76 ms 79 ms 79 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    15 111 ms 89 ms 84 ms lp.soe.com [64.37.171.24]

    Trace complete.

    Tried tracert'ing during the peak time in my area (California) and it times out and can't reach the next hop after SanJose5.Level3
    Komotz, Sep 9, 2014
    #245

  6. Flyaxl

    just did a tracert

    Détermination de l'itinéraire vers lp.soe.com [64.37.171.24]
    avec un maximum de 30 sauts :
    1 1 ms 1 ms 1 ms 192.168.1.1
    2 44 ms 44 ms 44 ms 192.168.153.1
    3 44 ms 44 ms 44 ms 145.Red-81-46-67.staticIP.rima-tde.net [81.46.67.145]
    4 75 ms 75 ms 75 ms 213.140.50.85
    5 103 ms 101 ms 100 ms Xe7-1-2-0-grtpareq1.red.telefonica-wholesale.net[84.16.12.26]
    6 184 ms 181 ms 183 ms Xe3-1-6-0-grtwaseq1.red.telefonica-wholesale.net[94.142.116.213]
    7 218 ms 218 ms 216 ms Xe-0-1-0-0-grtdaleq4.red.telefonica-wholesale.net [94.142.120.93]
    8 221 ms 218 ms 219 ms xe-10-2-0.edge5.Dallas3.Level3.net [4.59.36.53]
    9 * * * Délai d'attente de la demande dépassé. (Timed out)
    10 * * * Délai d'attente de la demande dépassé. (Timed out)
    11 * * * Délai d'attente de la demande dépassé. (Timed out)
    12 260 ms 264 ms 269 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    13 278 ms 264 ms 265 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    14 250 ms 254 ms 252 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    15 255 ms 266 ms 260 ms lp.soe.com [64.37.171.24]
    Itinéraire déterminé.


    ____________________________________________________________________________________

    Détermination de l'itinéraire vers amspsn-liv-gw01.planetside2.com [69.174.194.165]
    avec un maximum de 30 sauts :
    1 1 ms 1 ms 1 ms 192.168.1.1
    2 45 ms 43 ms 44 ms 192.168.153.1
    3 44 ms 44 ms 44 ms 145.Red-81-46-67.staticIP.rima-tde.net [81.46.67.145]
    4 * * * Délai d'attente de la demande dépassé. (Timed out)
    5 95 ms 123 ms 96 ms Xe5-1-4-0-grtpareq1.red.telefonica-wholesale.net [84.16.12.10]
    6 92 ms 91 ms 91 ms xe-11-2-0.edge3.Paris1.Level3.net [212.73.205.221]
    7 * * * Délai d'attente de la demande dépassé. (Timed out)
    8 * * * Délai d'attente de la demande dépassé. (Timed out)
    9 * * * Délai d'attente de la demande dépassé. (Timed out)
    10 * * * Délai d'attente de la demande dépassé. (Timed out)
    11 * * * Délai d'attente de la demande dépassé. (Timed out)
    12 * * * Délai d'attente de la demande dépassé. (Timed out)
    13 115 ms 116 ms 114 ms ae-240-3616.edge6.Amsterdam1.Level3.net [4.69.162.254]
    14 105 ms 106 ms 107 ms SONY-ONLINE.edge6.Amsterdam1.Level3.net [212.72.46.190]
    15 115 ms 114 ms 117 ms amspsn-liv-gw01.planetside2.com [69.174.194.165]

    Itinéraire déterminé.
    Flyaxl, Sep 9, 2014
    #246 Last edited by Flyaxl, Sep 9, 2014

  7. Zer0G249

    Here is mine and it'll seem to be the worst case.

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

    1 * * * Request timed out.
    2 33 ms 30 ms 30 ms 117.198.48.1
    3 47 ms 43 ms 226 ms 218.248.168.198
    4 88 ms 86 ms 87 ms 59.163.207.81.static.chennai.vsnl.net.in [59.163
    .207.81]
    5 112 ms 112 ms 109 ms 172.31.29.245
    6 * 113 ms 109 ms ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38
    .5]
    7 * * * Request timed out.
    8 222 ms 225 ms 226 ms if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.21
    7.6]
    9 219 ms 224 ms 224 ms if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.1
    7]
    10 358 ms 361 ms 350 ms 80.231.153.66
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 320 ms 318 ms 323 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 338 ms 322 ms 320 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    23 321 ms 321 ms 319 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    24 321 ms 320 ms 321 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    25 321 ms 319 ms 321 ms lp.soe.com [64.37.171.24]

    Trace complete.

    My ISP is BSNL. I'm from India. I sincerely think though SOE is going to do nothing about this issue since there are more people not facing it than there are who are facing it.
    Zer0G249, Sep 10, 2014
    #247

  8. Root

    Having some connection issues tonight. I saw this thread and here's my traceroute, it's not in good shape:

    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.200.1
    3 * * * Request timed out.
    4 8 ms 8 ms 7 ms 172.17.122.34
    5 8 ms 9 ms 7 ms WS-ZT-1.CIN1.core.fuse.net [216.68.14.52]
    6 27 ms 28 ms 29 ms CIN1.ASH1.core.fuse.net [216.68.14.51]
    7 34 ms 32 ms 30 ms xe-4-2-0.was14.ip4.gtt.net [173.241.131.157]
    8 91 ms 96 ms 106 ms te-7-2.car4.Washington1.Level3.net [4.68.110.97]
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 128 ms 131 ms 133 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    13 130 ms 130 ms 130 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 194 ms 116 ms 113 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    17 126 ms 120 ms 116 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

    18 132 ms 132 ms 127 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    19 130 ms 126 ms 128 ms lp.soe.com [64.37.171.24]
    Root, Sep 10, 2014
    #248

  9. GiorgyGR

    Here is mine too.Isn't looks good as well


    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 9 ms 6 ms 6 ms 80.106.108.37
    3 6 ms 5 ms 5 ms 79.128.245.29
    4 7 ms 7 ms 7 ms athe-crsb-peir7609b-1.backbone.otenet.net [79.12
    8.227.165]
    5 9 ms 7 ms 7 ms ten0-1-0-0-crs01.ath.OTEGlobe.net [62.75.3.1]
    6 52 ms 51 ms 51 ms 62.75.4.102
    7 52 ms 61 ms 52 ms xe-7-3-0.edge5.London1.Level3.net [212.187.138.1
    17]
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 185 ms 184 ms 184 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 186 ms 211 ms 184 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    18 188 ms 187 ms 187 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

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

    Trace complete.
    GiorgyGR, Sep 11, 2014
    #249

  10. HD0087

    ISP: TeliaSonera
    Location: Finland
    Problems start at level3 & telia colocation.

    AVG:
    1 <1 ms <1 ms <1 ms router
    2 17 ms 17 ms 17 ms noneofyourbusiness.dhcp.inet.fi [?]
    3 19 ms 19 ms 19 ms hls-b2-link.telia.net [62.115.140.98]
    4 27 ms 27 ms 27 ms s-bb3-link.telia.net [80.91.250.62]
    5 26 ms 27 ms 26 ms s-b6-link.telia.net [62.115.136.25]
    6 26 ms * * level3-ic-155475-s-b2.c.telia.net [213.248.99.134]
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 56 ms 56 ms 56 ms ae-45-45.ebr1.Amsterdam1.Level3.net [4.69.143.197]
    11 * * * Request timed out.
    12 55 ms 55 ms 55 ms ae-128-3514.edge6.Amsterdam1.Level3.net [4.69.162.230]
    13 53 ms 53 ms 53 ms SONY-ONLINE.edge6.Amsterdam1.Level3.net [212.72.46.190]
    14 55 ms 55 ms 55 ms amspsn-liv-gw01.planetside2.com [69.174.194.165]
    WCS:
    1 <1 ms <1 ms <1 ms router
    2 17 ms 17 ms 17 ms noneofyourbusiness.dhcp.inet.fi [?]
    3 19 ms 19 ms 18 ms hls-b2-link.telia.net [62.115.140.100]
    4 27 ms 27 ms 27 ms s-bb3-link.telia.net [80.91.250.62]
    5 27 ms 26 ms 27 ms s-b6-link.telia.net [62.115.139.107]
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 56 ms 56 ms 56 ms ae-45-45.ebr1.Amsterdam1.Level3.net [4.69.143.197]
    11 * * * Request timed out.
    12 54 ms 54 ms 54 ms ae-128-3514.edge6.Amsterdam1.Level3.net [4.69.162.230]
    13 53 ms 53 ms 53 ms SONY-ONLINE.edge6.Amsterdam1.Level3.net [212.72.46.190]
    14 56 ms 56 ms 56 ms amspsn-liv-gw01.planetside2.com [69.174.194.165]
    HD0087, Sep 11, 2014
    #250

  11. GalaxyKillers

    Tracing route to lp.soe.com [64.37.171.24]
    over a maximum of 30 hops:
    1 1 ms 1 ms <1 ms livebox.home [192.168.1.1]
    2 15 ms 10 ms 10 ms 197.225.32.1
    3 10 ms 11 ms 11 ms 196.27.70.105
    4 41 ms 23 ms 12 ms tengig4-1.201-fl.telecomplus.net [196.20.254.173
    ]
    5 129 ms 81 ms 154 ms 1.9.241.193
    6 386 ms 270 ms 292 ms 10.55.192.0
    7 264 ms 264 ms 264 ms xe-7-1-3.edge1.SanJose2.Level3.net [4.28.172.89]
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 367 ms 371 ms 365 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
    14 368 ms 365 ms 372 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
    6.50]
    15 367 ms 366 ms 367 ms lp.soe.com [64.37.171.24]
    sometimes this works sometimes I get >10000 ms
    GalaxyKillers, Sep 11, 2014
    #251

  12. ninzor

    maybe they should move this post to reddit since they obviously dont read these forums.
    ninzor, Sep 11, 2014
    #252

  13. SenorGomez

    You know somethings wrong when the players can only get feedback from the developer team on a low of a place as reddit.
    Think the only feedback we get on here are thread locks based on non-constructive/progressive discussion.
    In their eyes its better to keep the forum "moderated" and clean of anything that might start some slander of good image, instead of confronting the issues at hand that show like a sore thumb.
    SenorGomez, Sep 11, 2014
    #253 Last edited by SenorGomez, Sep 11, 2014

  14. SomeRandomNewbie

    From the UK - note that first hops are a bit slow at the moment as I'm on a 3G connection and the supermarket 2 doors down is going to be hammering the cell tower (midday on a sunday, busy time for them).

    Code:
    Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:
 
  1  105 ms    79 ms    79 ms  172.23.227.65
  2    86 ms    89 ms    99 ms  172.30.146.163
  3    87 ms    99 ms  119 ms  188.31.255.38.threembb.co.uk [188.31.255.38]
  4  118 ms  169 ms  199 ms  188.31.255.89.threembb.co.uk [188.31.255.89]
  5  127 ms  189 ms  149 ms  ae4.man11.ip4.gtt.net [141.136.98.193]
  6  167 ms  189 ms  109 ms  xe-3-0-5.lon10.ip4.gtt.net [141.136.106.253]
  7  127 ms    89 ms    79 ms  ae8.edge4.London.Level3.net [4.68.111.25]
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
14  1293 ms  1134 ms  850 ms  ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
15    *        *        *    Request timed out.
16    *        *        *    Request timed out.
17  1009 ms  268 ms  389 ms  ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
18  338 ms  219 ms  1259 ms  ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
19  237 ms  289 ms  239 ms  SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
20  227 ms  209 ms  229 ms  lp.soe.com [64.37.171.24]
 
 
Trace complete.
    To what I assume is Cobalt...
    Code:
    Tracing route to amspsn-liv-gw02.planetside2.com [69.174.194.166]
over a maximum of 30 hops:
 
  1    86 ms    69 ms    79 ms  172.23.227.1
  2  201 ms  159 ms  119 ms  172.30.146.163
  3  178 ms  119 ms    79 ms  188.31.255.38.threembb.co.uk [188.31.255.38]
  4  178 ms    89 ms    79 ms  188.31.255.89.threembb.co.uk [188.31.255.89]
  5  117 ms    89 ms    89 ms  ae4.man11.ip4.gtt.net [141.136.98.193]
  6  128 ms    89 ms    89 ms  xe-3-0-5.lon10.ip4.gtt.net [141.136.106.253]
  7    96 ms    99 ms  129 ms  ae8.edge4.London.Level3.net [4.68.111.25]
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12  2488 ms    99 ms  139 ms  ae-240-3616.edge6.Amsterdam1.Level3.net [4.69.162.254]
13  127 ms  169 ms  209 ms  SONY-ONLINE.edge6.Amsterdam1.Level3.net [212.72.46.190]
14  197 ms  159 ms    99 ms  amspsn-liv-gw02.planetside2.com [69.174.194.166]
 
 
Trace complete.
    I tend to play later at night, when there're less people about. Still get a lot of yellows (poor connection) and random ping spikes into the 10k+ range, so the packet losses look about right.
    SomeRandomNewbie, Sep 14, 2014
    #254 Last edited by SomeRandomNewbie, Sep 14, 2014

  15. Napsterbater

    People posting tracerts with a <100ms latency at the destination but have a "Request timed out" in the middle are wasting space in this thread.

    Also pathping will not work when a tracert has a "Request timed out" in the middle, it is a limitation of pathping not an indication of a problem.

    Note this is an example of a perfectly fine tracert. Notice the "Request timed out" but also notice hops 12 comes back just fine with a good latency.

    Code:
    C:\Windows\system32>tracert 69.174.216.27
 
Tracing route to 69.174.216.27 over a maximum of 30 hops
 
  1    1 ms    <1 ms    3 ms  car1.napshome.local [10.0.1.3]
  2    3 ms    3 ms    12 ms  gpon-local.xlr8bb.com [10.40.0.1]
  3    2 ms    4 ms    2 ms  gpon-local.xlr8bb.com [172.16.1.2]
  4    11 ms    10 ms    11 ms  38.122.47.121
  5    14 ms    13 ms    15 ms  te0-7-0-5.ccr21.atl04.atlas.cogentco.com [154.54
.85.234]
  6    10 ms    10 ms    11 ms  level3.atl04.atlas.cogentco.com [154.54.12.138]
 
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    24 ms    23 ms    26 ms  ae-1-80.edge1.washington1.level3.net [4.69.149.1
41]
11    25 ms    27 ms    26 ms  vl124.asheqnx-2.sonyonline.net [63.215.136.202]
 
12    26 ms    24 ms    23 ms  69.174.216.27
 
Trace complete.
    Here is the pathping, notice it can not make it to the destination, again nothing is broken its is just unable to work past a non responding hop (Request timed out).

    Code:
    C:\Windows\system32>pathping 69.174.216.27
 
Tracing route to 69.174.216.27 over a maximum of 30 hops
 
  0  Bos.napshome.local [10.0.1.112]
  1  car1.napshome.local [10.0.1.3]
  2  gpon-local.xlr8bb.com [10.40.0.1]
  3  gpon-local.xlr8bb.com [172.16.1.2]
  4  38.122.47.121
  5  te0-7-0-5.ccr21.atl04.atlas.cogentco.com [154.54.85.234]
  6    *    level3.atl04.atlas.cogentco.com [154.54.12.138]
  7    *        *        *
Computing statistics for 150 seconds...
            Source to Here  This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                          Bos.napshome.local [10.0.1.112]
                                0/ 100 =  0%  |
  1    1ms    0/ 100 =  0%    0/ 100 =  0%  car1.napshome.local [10.0.1.3]
                                0/ 100 =  0%  |
  2    3ms    0/ 100 =  0%    0/ 100 =  0%  gpon-local.xlr8bb.com [10.40.0.1]
 
                                0/ 100 =  0%  |
  3    3ms    0/ 100 =  0%    0/ 100 =  0%  gpon-local.xlr8bb.com [172.16.1.2]
 
                                0/ 100 =  0%  |
  4  17ms    0/ 100 =  0%    0/ 100 =  0%  38.122.47.121
                                0/ 100 =  0%  |
  5  12ms    0/ 100 =  0%    0/ 100 =  0%  te0-7-0-5.ccr21.atl04.atlas.cogent
co.com [154.54.85.234]
                                0/ 100 =  0%  |
  6  14ms    0/ 100 =  0%    0/ 100 =  0%  level3.atl04.atlas.cogentco.com [1
54.54.12.138]
 
Trace complete.
    Napsterbater, Sep 14, 2014
    #255

  16. bubbleawsome

    I've been getting horrible pings (1800ms+) from knowology. Turns out I'm routing through level 3. Any help?
    bubbleawsome, Sep 14, 2014
    #256

  17. Napsterbater

    What PS2 server?
    Napsterbater, Sep 14, 2014
    #257

  18. bubbleawsome

    Emerald. I think I could change that by going to US west or EU. (I've got a character on EU, don't ask. :p)
    bubbleawsome, Sep 14, 2014
    #258

  19. Napsterbater

    Then run a Traceroute to 69.174.216.27 and post it.
    Napsterbater, Sep 14, 2014
    #259

  20. bubbleawsome

    [IMG]

    Hm, seems not to be a problem with Emerald then. (lp.soe.com did) I'll get a screen of my 1400 ping though.
    bubbleawsome, Sep 14, 2014
    #260
Page 13 of 23
Thread Status:
Not open for further replies.