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

  1. Napsterbater



    Nope, what you are seeing is a router configured or unable to respond to ICMP request, it it was a problem everything past it would show issues on the trace.

    Based on that trace, it looks like you're getting to the server fine. Something is most likely up with the server itself.
    Napsterbater, Oct 12, 2014
    #321

  2. AgentRed

    I play on Emerald and live in TX.
    AgentRed, Oct 12, 2014
    #322

  3. Napsterbater


    Then you need to trace to 69.174.216.21
    Napsterbater, Oct 12, 2014
    #323

  4. AgentRed

    It says VA
    AgentRed, Oct 12, 2014
    #324

  5. Napsterbater

    Thats where the Emerald server is.
    Napsterbater, Oct 12, 2014
    #325

  6. WurbleFlurble

    updated tracert to Emerald's ip from Kentucky:
    C:\Users\Tyler>tracert 69.174.216.27

    Tracing route to 69.174.216.27 over a maximum of 30 hops

    1 3 ms 5 ms 28 ms 192.168.0.1
    2 191 ms 40 ms 70 ms 69.137.126.1
    3 235 ms 26 ms 27 ms te-1-2-sr01.elizabethtwn.ky.nash.comcast.net [68
    .85.50.173]
    4 28 ms 48 ms 67 ms te-3-1-sr02.elizabethtwn.ky.nash.comcast.net [68
    .86.176.229]
    5 117 ms 29 ms 25 ms xe-7-0-0-0-ar03.nashville.tn.nash.comcast.net [6
    8.86.176.225]
    6 108 ms 103 ms 137 ms ae-2-0-ar01.goodslettvll.tn.nash.comcast.net [68
    .85.174.238]
    7 58 ms 58 ms 51 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net
    [68.86.90.101]
    8 53 ms 50 ms 155 ms pos-0-11-0-0-pe01.56marietta.ga.ibone.comcast.ne
    t [68.86.88.186]
    9 215 ms 153 ms 106 ms 173.167.56.2
    10 293 ms 175 ms 233 ms tge7-2.fr3.iad.llnw.net [69.28.171.233]
    11 132 ms 276 ms 299 ms sony.ge4-12.fr3.iad.llnw.net [68.142.111.254]
    12 371 ms 114 ms 67 ms 69.174.216.27

    Trace complete.
    I also opened a support ticket about this on SOEs customer support and they said that my ISP(comcast) had bad connections to Level3 and that i'd have to contact them about it. (and everyone knows that Comcast's customer support is absolute garbage)
    WurbleFlurble, Oct 12, 2014
    #326 Last edited by WurbleFlurble, Oct 12, 2014

  7. Napsterbater



    You are having some drastic latency variations very early in your traceroute.

    I'm gonna guess you are on WiFi, you should see about picking a better/cleaner channel as a first step.
    Napsterbater, Oct 12, 2014
    #327

  8. Archemoruss

    To the Miller server -

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

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 7 ms 6 ms 7 ms 10.188.160.1
    3 26 ms * * 172.18.12.94
    4 10 ms * 14 ms 172.17.1.249
    5 15 ms * * 172.17.1.193
    6 14 ms 10 ms 11 ms ACCESS-MR-01-tengig10-6.ip4.012.net.il [212.199.
    24.217]
    7 11 ms 17 ms 15 ms BRDR-CORE-MR-xe-3-1-0-3011.ip4.012.net.il [212.1
    99.5.62]
    8 13 ms 12 ms 11 ms BRDR-CORE-MR-xe-3-1-0-3011.ip4.012.net.il [212.1
    99.5.62]
    9 11 ms 12 ms 14 ms BRDR-CORE-MR-ae0-3024.ip4.012.net.il [212.199.5.
    105]
    10 69 ms 64 ms 67 ms 80.179.166.142.static.012.net.il [80.179.166.142
    ]
    11 63 ms 64 ms 70 ms EDGE-FRA-02-ge-4-0-0-282.ip4.012.net.il [80.179.
    166.161]
    12 63 ms 66 ms 74 ms decix-2.eu.equinix.net [80.81.193.234]
    13 78 ms 78 ms 77 ms po9-1425.bg1.am1.eu.equinix.net [217.68.145.26]

    14 79 ms 79 ms 77 ms po7.bg1.am3.eu.equinix.net [94.103.16.86]
    15 77 ms 76 ms 77 ms po2.bg2.am3.eu.equinix.net [94.103.16.122]
    16 74 ms 70 ms 69 ms sony.customer.am3.eu.equinix.net [5.175.82.94]
    17 74 ms 71 ms 71 ms amspsn-liv-gw04.planetside2.com [69.174.194.168]


    Trace complete.


    To the lp.SoE one -

    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 8 ms 11 ms 9 ms 10.188.160.1
    3 * * * Request timed out.
    4 12 ms 11 ms * 172.17.1.245
    5 15 ms * * 172.17.1.189
    6 10 ms 12 ms 11 ms ACCESS-MR-01-tengig10-6.ip4.012.net.il [212.199.24.217]
    7 14 ms 10 ms 20 ms BRDR-CORE-MR-xe-3-1-0-3011.ip4.012.net.il [212.199.5.62]
    8 16 ms 12 ms 11 ms BRDR-CORE-MR-xe-3-1-0-3011.ip4.012.net.il [212.199.5.62]
    9 17 ms 13 ms 13 ms BRDR-CORE-MR-ae0-3024.ip4.012.net.il [212.199.5.105]
    10 74 ms 65 ms 67 ms EDGE-FRA-01-so-2-1-0-0-0.ip4.012.net.il [80.179.166.17]
    11 64 ms 70 ms 63 ms ffm-s2-rou-1041.DE.eurorings.net [134.222.142.1]
    12 67 ms 64 ms 62 ms dialup-212.162.19.61.frankfurt1.mik.net [212.162.19.61]
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 212 ms 214 ms 212 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
    19 212 ms 213 ms 212 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 210 ms 211 ms 212 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
    23 212 ms 212 ms 215 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
    24 211 ms 214 ms 211 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
    25 213 ms 212 ms 212 ms lp.soe.com [64.37.171.24]

    Trace complete.


    Canceled my subscription already, I'm not paying to play an FPS with 667,000 ms.
    Currently Im playing the subscription fee to log in once per day and claim my daily certs. It's over.
    Archemoruss, Oct 14, 2014
    #328

  9. AgentRed

    same thing I have made a few different support tickets on it one said make a bug report and others to some it up to keep a date on the thread, "Unfortunately, we cannot address an issue that appears to be occurring with Level 3", and "I certainly hope it can be resolved soon" so when my sub is about to run out I will not renew unless this game is fixed. I lost a lot of outfit members to this D:
    AgentRed, Oct 14, 2014
    #329

  10. WurbleFlurble

    i did that before making that tracert. im on the cleanest channel i could find. Didn't improve or degrade my ping in any way.
    WurbleFlurble, Oct 16, 2014
    #330

  11. Napsterbater

    Then you need to accept that your WiFi in its current state maybe contribute to issues with latency/lag

    Do some more rearranging/troubleshooting of your wifi network until to have stable Latency to Your router, then double check for stable latency to you ISPs first hop.

    These commands can help with that. Just watch for a steady response time.

    " ping -t 192.168.0.1 " (if you get frequent big jumps here this is a WiFi Issue)
    and
    " ping -t 69.137.126.1 " (note replace that IP with the current IP in the 2nd hop of your tracert and if you get frequent big jumps here this is possible a ISP Issue or your router)
    Napsterbater, Oct 16, 2014
    #331

  12. WurbleFlurble

    Don't know if I did this right but here's what i got:
    C:\Users\Tyler>ping -t 192.168.0.1

    Pinging 192.168.0.1 with 32 bytes of data:
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=86ms TTL=6
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    C:\Users\Tyler>ping -t 69.137.126.1

    Pinging 69.137.126.1 with 32 bytes of data:
    Reply from 69.137.126.1: bytes=32 time=22ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=20ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=23ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=22ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=19ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=20ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=8ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=21ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=12ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=14ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=21ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=14ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=29ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=15ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=16ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=78ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=21ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=14ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=12ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=8ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=22ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=22ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=8ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=20ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=12ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=19ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=17ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=20ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=20ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=12ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=20ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=12ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=14ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=12ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=22ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=12ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    WurbleFlurble, Oct 16, 2014
    #332

  13. Napsterbater

    That looks pretty decent, with only occasional hiccups, if you can run it again during prime time, 7-9pm or so.
    Napsterbater, Oct 16, 2014
    #333

  14. WurbleFlurble

    i will if i remember.
    WurbleFlurble, Oct 16, 2014
    #334

  15. WurbleFlurble

    C:\Users\Tyler>ping -t 192.168.0.1

    Pinging 192.168.0.1 with 32 bytes of data:
    Reply from 192.168.0.1: bytes=32 time=101ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

    C:\Users\Tyler>ping -t 69.137.126.1

    Pinging 69.137.126.1 with 32 bytes of data:
    Reply from 69.137.126.1: bytes=32 time=20ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=8ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=26ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=22ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=15ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=14ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=18ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=24ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=16ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=19ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=22ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=23ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=12ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=8ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=22ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=16ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=8ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=16ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=21ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=13ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=10ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=11ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=9ms TTL=254
    Reply from 69.137.126.1: bytes=32 time=20ms TTL=254
    WurbleFlurble, Oct 16, 2014
    #335

  16. ulceroso

    Is the lag ever going to be solved? After a week break the game is even worse. I regret every single euro sank on this game.
    ulceroso, Oct 18, 2014
    #336

  17. WurbleFlurble

    I will say that the issue (at least for me) seems to be ever so slowly fixing itself. I can now usually get in about an hour or two in before my ping will decide jump to unplayable levels.
    WurbleFlurble, Oct 18, 2014
    #337

  18. TownCryer8

    Code:
    Tracing route to amspsn-liv-gw01.planetside2.com [69.174.194.165]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    22 ms    23 ms    23 ms  abts-north-static-072.220.160.122.airtelbroadban
d.in [122.160.220.72]
  3    *        *        *    Request timed out.
  4    23 ms    23 ms    24 ms  125.19.22.149
  5  269 ms  317 ms  267 ms  203.101.100.190
  6  274 ms  264 ms  264 ms  182.79.243.69
  7  137 ms    62 ms    61 ms  182.79.255.69
  8  268 ms  268 ms  268 ms  aes-static-194.36.144.59.airtel.in [59.144.36.19
4]
  9  307 ms  306 ms  306 ms  TenGigabitEthernet8-4.ar7.NYC1.gblx.net [64.211.
60.197]
10  387 ms  386 ms  385 ms  vlan70.csw2.NewYork1.Level3.net [4.69.155.126]
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *      384 ms    *    ae-45-45.ebr2.Amsterdam1.Level3.net [4.69.143.69
]
14    *        *        *    Request timed out.
15  434 ms  400 ms  407 ms  ae-237-3613.edge6.Amsterdam1.Level3.net [4.69.16
2.242]
16  399 ms  399 ms  399 ms  SONY-ONLINE.edge6.Amsterdam1.Level3.net [212.72.
46.190]
17  384 ms  385 ms  386 ms  amspsn-liv-gw01.planetside2.com [69.174.194.165]
 
Trace complete.
    This crap again. Taking an unnecessary trip to New York, when I'm trying to reach Amsterdam from India. Please fix this, game is unplayable!
    TownCryer8, Oct 18, 2014
    #338

  19. Napsterbater

    That is because your ISP is peering with Level3 in New York, and your ISP has to send its traffic to Level3 to get to SOE, this is a problem with your ISP.
    Napsterbater, Oct 18, 2014
    #339

  20. taurangaNZ

    I thought hop12 and hop13 were normal.. I thought all routers did not need to reply to ICMP, its optional right? hop16 is reachable, then why did SOE support reply with their reply below like that??

    Code:
    Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:
 
  1    11 ms    3 ms    4 ms  BoB.Orcon [10.1.1.1]
  2    36 ms    24 ms    16 ms  euba.bng1.tvc.orcon.net.nz [60.234.8.5]
  3    15 ms    15 ms    15 ms  xe-3-3-0.cre1.sky.orcon.net.nz [121.98.9.72]
  4    14 ms    14 ms    14 ms  121.98.9.137
  5    16 ms    15 ms    15 ms  ae1-0.cre2.nct.odyssey.net.nz [121.99.12.3]
  6    15 ms    20 ms    28 ms  202.50.238.66
  7    15 ms    15 ms    15 ms  202.50.238.65
  8    15 ms    17 ms    18 ms  ae0-10.tkbr12.global-gateway.net.nz [203.96.120.105]
  9  141 ms  140 ms  139 ms  203.96.120.142
10  140 ms  144 ms  139 ms  ae0-10.lebr8.global-gateway.net.nz [202.50.232.42]
11  139 ms  139 ms  140 ms  ae51.edge2.LosAngeles9.Level3.net [4.53.230.13]
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
14  145 ms  145 ms  144 ms  ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
15  146 ms  147 ms  146 ms  SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
16  177 ms  177 ms  177 ms  lp.soe.com [64.37.171.24]
    taurangaNZ, Oct 20, 2014
    #340
Page 17 of 23
Thread Status:
Not open for further replies.