1. Click here to join our community discord server.

Network issues

Discussion in 'Announcements' started by marvel, Sep 6, 2011.

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

    marvel Head Administrator Staff Member

    Well, I made an important discovery tonight, after struggling for three nights now (or more) with server connectivity I finally found out the problem. The problem is not the St. Louis or Chicago server, but the Leaseweb database / webserver.

    There's huge packet loss to this system, not only from the USA but even from the EU gameserver that sits in the same datacenter. Package loss averages from 30 - 40%

    There seems to be one specific router to blame, the 85.17.100.180. Not all servers connect to our DB server using this router, so that's why not all servers have the same issues.

    Code:
                                           Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. hosted.by.leaseweb.com            0.0%    23    4.6   0.6   0.3   4.6   1.0
 2. xe3-0-3.hvc1.evo.leaseweb.net     0.0%    23    0.1   0.7   0.1  11.6   2.4
 3. 85.17.100.237                     0.0%    23    1.2   1.3   0.9   2.1   0.3
 4. 85.17.100.180                    40.9%    22    0.7  13.7   0.5 169.9  46.9
 5. mail.mgftw.com                    0.0%    22   19.2  18.5  16.2  20.0   1.1
    A ticket has been submitted with Leaseweb but since we obv. don't have an expensive SLA they are checking it tomorrow during office hours.

    I'll keep you updated. Chicago remains down until this has been resolved (Vicious Infected excluded since that one doesn't rely on a stable DB connection so much).
     
    marvel, Sep 6, 2011
    #1
  2. L1teHawk

    L1teHawk Senior Member

    Let me know if you ever need me to drive down there :)
     
    L1teHawk, Sep 6, 2011
    #2
  3. Kitties

    Kitties Head Administrator

    traceroute 85.17.100.180
    traceroute to 85.17.100.180 (85.17.100.180), 64 hops max, 52 byte packets
    1 ***nope.avi*** 0.658 ms 0.286 ms 0.269 ms
    2 ***nope.avi*** 1.482 ms 0.991 ms 1.127 ms
    3 ***nope.avi*** 0.904 ms 0.850 ms 1.668 ms
    4 cr2-sea-a-g1-7.bb.spectrumnet.us (208.76.153.45) 10.027 ms 9.993 ms 9.876 ms
    5 te4-4.ccr01.sea02.atlas.cogentco.com (38.104.126.217) 9.823 ms 9.989 ms 10.192 ms
    6 te8-1.ccr01.sea01.atlas.cogentco.com (154.54.44.85) 10.214 ms
    te8-3.ccr01.sea01.atlas.cogentco.com (154.54.44.89) 10.038 ms
    te7-4.ccr01.sea01.atlas.cogentco.com (154.54.3.33) 10.127 ms
    7 te7-2.ccr01.smf01.atlas.cogentco.com (154.54.47.193) 26.277 ms
    te3-1.ccr01.pdx02.atlas.cogentco.com (154.54.40.117) 13.933 ms
    te7-4.ccr01.smf01.atlas.cogentco.com (154.54.40.105) 26.286 ms
    8 te3-4.ccr01.smf01.atlas.cogentco.com (154.54.40.109) 25.747 ms 25.819 ms
    te0-0-0-5.mpd21.sfo01.atlas.cogentco.com (154.54.45.57) 28.663 ms
    9 te0-0-0-5.mpd22.sfo01.atlas.cogentco.com (154.54.24.113) 29.063 ms
    te3-2.ccr01.oak01.atlas.cogentco.com (154.54.45.21) 28.056 ms
    te4-4.mpd01.sjc01.atlas.cogentco.com (154.54.2.54) 29.746 ms
    10 te9-4.mpd01.sjc01.atlas.cogentco.com (66.28.4.182) 30.045 ms
    te9-2.mpd01.sjc01.atlas.cogentco.com (66.28.4.150) 29.956 ms
    te0-0-0-5.mpd22.sfo01.atlas.cogentco.com (154.54.24.113) 29.197 ms
    11 te9-2.mpd01.sjc01.atlas.cogentco.com (66.28.4.150) 30.065 ms
    te8-1.mpd01.sjc03.atlas.cogentco.com (154.54.41.202) 30.999 ms
    sjo-bb1-link.telia.net (80.239.196.189) 29.846 ms
    12 sjo-bb1-link.telia.net (80.239.196.189) 30.097 ms 30.154 ms
    te8-1.mpd01.sjc03.atlas.cogentco.com (154.54.41.202) 30.518 ms
    13 ash-bb1-link.telia.net (80.91.248.205) 102.512 ms
    sjo-bb1-link.telia.net (80.239.196.189) 30.692 ms
    ash-bb1-link.telia.net (80.91.248.205) 92.775 ms
    14 ldn-bb1-link.telia.net (80.91.246.69) 171.842 ms 171.877 ms
    ash-bb1-link.telia.net (80.91.248.205) 92.878 ms
    15 adm-b4-link.telia.net (213.155.130.219) 179.806 ms 179.664 ms
    ldn-bb1-link.telia.net (80.91.246.69) 171.929 ms
    16 adm-b4-link.telia.net (213.155.130.219) 179.726 ms 181.379 ms 180.035 ms
    17 * * leaseweb-ic-129604-adm-b4.c.telia.net (213.248.91.222) 182.132 ms
    18 leaseweb-ic-129604-adm-b4.c.telia.net (213.248.91.222) 181.874 ms * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    31 * * *
    32 * * *
    33 * * *
    34 * * *
    35 * * *
    36 * * *
    37 * * *
    38 * * *
    39 * * *
    40 * * *
    41 * * *
    42 * * *
    43 * * *
    44 * * *
    45 * * *
    46 * * *
    47 * * *
    48 * * *
    49 * * *
    50 * * *
    51 * * *
    52 * * *
    53 * * *
    54 * * *
    55 * * *
    56 * * *
    57 * * *
    58 * * *
    59 * * *
    60 * * *
    61 * * *
    62 * * *
    63 * * *
    64 * * *
     
    Kitties, Sep 6, 2011
    #3
  4. marvel

    marvel Head Administrator Staff Member

    \

    Yes beat the crap out of them please ;)

    Anyway Leaseweb contacted me they say there are no issues with the network so I have to look at the machine itself.
     
    marvel, Sep 7, 2011
    #4
  5. L1teHawk

    L1teHawk Senior Member

    Terrible. I live in Chicago and I get 125 ms to the server. If I connect to another server in Chicago, my ping never goes over 12 ms, let alone 50% packet loss.

    Other people seem to be having a problem with them too:
    http://www.webhostingtalk.com/showthread.php?t=1019871
     
    L1teHawk, Sep 9, 2011
    #5
  6. marvel

    marvel Head Administrator Staff Member

    I think you are pinging mail.mgftw.com which is in Haarlem, Netherlands ;)
     
    marvel, Sep 9, 2011
    #6
  7. jtork

    jtork Senior Member

    leaseweb sucks!! try evoswitch datacenter
     
    jtork, Sep 9, 2011
    #7
  8. marvel

    marvel Head Administrator Staff Member

    We use evoswitch right now....

    Sent from my Desire HD using Tapatalk
     
    marvel, Sep 10, 2011
    #8
Thread Status:
Not open for further replies.