Results 1 to 3 of 3

Thread: Routing problems

  1. #1
    BioMelt's Avatar



    Join Date
    Dec 18, 2009
    Last Online
    Jul 03, 2013
    Posts
    2
    Threads
    1



    Routing problems


    Hey seems today the server host is having some routing problems, Ping is high;

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    D:\Documents and Settings\ZooKeeper>ping 67.228.59.146

    Pinging 67.228.59.146 with 32 bytes of data:

    Reply from 67.228.59.146: bytes=32 time=152ms TTL=54
    Reply from 67.228.59.146: bytes=32 time=168ms TTL=54
    Reply from 67.228.59.146: bytes=32 time=160ms TTL=54
    Reply from 67.228.59.146: bytes=32 time=169ms TTL=54

    Ping statistics for 67.228.59.146:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 152ms, Maximum = 169ms, Average = 162ms

    D:\Documents and Settings\ZooKeeper>tracert 67.228.59.146

    Tracing route to tf22fortinstant.sourceop.com [67.228.59.146]
    over a maximum of 30 hops:

    1 2 ms 3 ms 2 ms mymodem [192.168.2.1]
    2 39 ms 47 ms 37 ms bas4-oshawa95_lo0_SYMP.net.bell.ca [64.230.200.1
    40]
    3 14 ms 11 ms 12 ms agg1-oshawa95_5-2-0_100.net.bell.ca [64.230.102.
    240]
    4 51 ms 82 ms 32 ms core4-toronto21_tengige0-9-1-0.net.bell.ca [64.2
    30.48.24]
    5 87 ms 28 ms 26 ms NEWCORE2-CHICAGOCP_so2-1-0-0.net.bell.ca [64.230
    .186.114]
    6 50 ms 55 ms 51 ms bx5-chicagodt_xe6-0-0.net.bell.ca [64.230.186.86
    ]
    7 36 ms 54 ms 45 ms te1-7.bbr01.eq01.chi01.networklayer.com [206.223
    .119.63]
    8 168 ms 184 ms 161 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.
    18.136]
    9 171 ms 148 ms 142 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.1
    8.253]
    10 65 ms 76 ms 78 ms po2.fcr05.sr06.dal01.networklayer.com [66.228.11
    8.223]
    11 163 ms 172 ms 172 ms tf22fortinstant.sourceop.com [67.228.59.146]

    Trace complete.

    D:\Documents and Settings\ZooKeeper>tracert 67.228.59.146

    Tracing route to tf22fortinstant.sourceop.com [67.228.59.146]
    over a maximum of 30 hops:

    1 13 ms 11 ms 2 ms mymodem [192.168.2.1]
    2 53 ms 40 ms 47 ms bas4-oshawa95_lo0_SYMP.net.bell.ca [64.230.200.1
    40]
    3 43 ms 62 ms 67 ms agg1-oshawa95_5-2-0_100.net.bell.ca [64.230.102.
    240]
    4 26 ms 33 ms 27 ms core4-toronto21_tengige0-9-1-0.net.bell.ca [64.2
    30.48.24]
    5 47 ms 45 ms 55 ms NEWCORE2-CHICAGOCP_so2-1-0-0.net.bell.ca [64.230
    .186.114]
    6 48 ms 63 ms 56 ms bx5-chicagodt_xe3-1-0-0.net.bell.ca [64.230.186.
    246]
    7 27 ms 25 ms 27 ms te1-7.bbr01.eq01.chi01.networklayer.com [206.223
    .119.63]
    8 174 ms 144 ms 160 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.
    18.136]
    9 161 ms 162 ms 165 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.1
    8.253]
    10 79 ms 102 ms 80 ms po2.fcr05.sr06.dal01.networklayer.com [66.228.11
    8.223]
    11 182 ms 177 ms 205 ms tf22fortinstant.sourceop.com [67.228.59.146]

    Trace complete.

    D:\Documents and Settings\ZooKeeper>tracert 67.228.59.146

    Tracing route to tf22fortinstant.sourceop.com [67.228.59.146]
    over a maximum of 30 hops:

    1 11 ms 21 ms 25 ms mymodem [192.168.2.1]
    2 39 ms 12 ms 12 ms bas4-oshawa95_lo0_SYMP.net.bell.ca [64.230.200.1
    40]
    3 45 ms 54 ms 52 ms agg1-oshawa95_5-2-0_100.net.bell.ca [64.230.102.
    240]
    4 61 ms 70 ms 90 ms core4-toronto21_tengige0-9-1-0.net.bell.ca [64.2
    30.48.24]
    5 69 ms 83 ms 70 ms NEWCORE2-CHICAGOCP_so2-1-0-0.net.bell.ca [64.230
    .186.114]
    6 88 ms 54 ms 64 ms bx4-chicagodt_xe0-1-1-0.net.bell.ca [64.230.186.
    110]
    7 52 ms 73 ms 68 ms te1-7.bbr01.eq01.chi01.networklayer.com [206.223
    .119.63]
    8 156 ms 184 ms 189 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.
    18.136]
    9 170 ms 176 ms 170 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.1
    8.253]
    10 219 ms 66 ms 105 ms po2.fcr05.sr06.dal01.networklayer.com [66.228.11
    8.223]
    11 187 ms 172 ms 168 ms tf22fortinstant.sourceop.com [67.228.59.146]

    Trace complete.

    D:\Documents and Settings\ZooKeeper>tracert 67.228.59.146

    Tracing route to tf22fortinstant.sourceop.com [67.228.59.146]
    over a maximum of 30 hops:

    1 22 ms 28 ms 16 ms mymodem [192.168.2.1]
    2 39 ms 38 ms 38 ms bas4-oshawa95_lo0_SYMP.net.bell.ca [64.230.200.1
    40]
    3 53 ms 41 ms 46 ms agg1-oshawa95_5-2-0_100.net.bell.ca [64.230.102.
    240]
    4 59 ms 51 ms 53 ms core4-toronto21_tengige0-9-1-0.net.bell.ca [64.2
    30.48.24]
    5 82 ms 42 ms 51 ms NEWCORE2-CHICAGOCP_so2-1-0-0.net.bell.ca [64.230
    .186.114]
    6 59 ms 69 ms 55 ms bx4-chicagodt_xe0-1-1-0.net.bell.ca [64.230.186.
    110]
    7 54 ms 76 ms 54 ms te1-7.bbr01.eq01.chi01.networklayer.com [206.223
    .119.63]
    8 173 ms 164 ms 168 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.
    18.136]
    9 163 ms 160 ms 138 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.1
    8.253]
    10 77 ms 65 ms 76 ms po2.fcr05.sr06.dal01.networklayer.com [66.228.11
    8.223]
    11 169 ms 168 ms 167 ms tf22fortinstant.sourceop.com [67.228.59.146]

    Trace complete.

    D:\Documents and Settings\ZooKeeper>tracert 67.228.59.146

    Tracing route to tf22fortinstant.sourceop.com [67.228.59.146]
    over a maximum of 30 hops:

    1 2 ms 2 ms 3 ms mymodem [192.168.2.1]
    2 46 ms 29 ms 46 ms bas4-oshawa95_lo0_SYMP.net.bell.ca [64.230.200.1
    40]
    3 97 ms 36 ms 42 ms agg1-oshawa95_5-2-0_100.net.bell.ca [64.230.102.
    240]
    4 46 ms 50 ms 51 ms core4-toronto21_tengige0-9-1-0.net.bell.ca [64.2
    30.48.24]
    5 53 ms 58 ms 53 ms NEWCORE2-CHICAGOCP_so2-1-0-0.net.bell.ca [64.230
    .186.114]
    6 61 ms 57 ms 65 ms bx5-chicagodt_xe3-1-0-0.net.bell.ca [64.230.186.
    246]
    7 68 ms 35 ms 28 ms te1-7.bbr01.eq01.chi01.networklayer.com [206.223
    .119.63]
    8 229 ms * * ae20.bbr01.eq01.dal03.networklayer.com [173.192.
    18.136]
    9 189 ms 171 ms 166 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.1
    8.253]
    10 51 ms 90 ms 77 ms po2.fcr05.sr06.dal01.networklayer.com [66.228.11
    8.223]
    11 160 ms 169 ms 158 ms tf22fortinstant.sourceop.com [67.228.59.146]

    Trace complete.

    D:\Documents and Settings\ZooKeeper>

    I did a number of TraceRT's just to prove thee point. Ping is just way to high and erratic to play today, maybe contact the host?

    (oh and I'm changing my home IP right now.

  2. #2
    Snarf's Avatar



    Join Date
    Nov 13, 2009
    Last Online
    Sep 10, 2017
    Posts
    2,833
    Threads
    103

        
    Steam: 76561198003556028 
    Steam join date: Dec 2, 2008
    Steam Level: 16
    Profile Status: Public



    For the record, you should always let it run pings for at least a minute. Also keep in mind pinging is going to be a little less accurate because it is a game server not a webserver, so it's not supposed to have new visitors on such an extreme level.
    Far as the actual server goes, I can't really say. It might be something on your end or something on sourceop's end. I don't run it so I can't really comment.
    I was a commando you know.

  3. #3
    BioMelt's Avatar



    Join Date
    Dec 18, 2009
    Last Online
    Jul 03, 2013
    Posts
    2
    Threads
    1




    Well its fixed now, I ran tracert after ping and you can clearly see "ae20.bbr01.eq01.dal03.networklayer.com [173.192.
    18.136] " is where the problem was.

    As I said in the OP it was a problem with the host routing.

Tags for this Thread