Welcome to the Rise of Agon Community

Create an account today to engage in discussions and community events on the Rise of Agon forums.

New Server Test IPs

Discussion in 'General Discussion' started by Andrew, Mar 19, 2017.

  1. RootedOak

    RootedOak Oak Lord
    Legend

    Joined:
    Oct 29, 2015
    Messages:
    3,041
    Likes Received:
    4,086
    @Andrew I'm working on checking all the routes that are listed in the OP.

    Are there any providers available in the Ashburn, VA area? I think that's a major east coast hub just one hop outside of New Jersey. I live just east of Pittsburgh, PA and my route to the current server goes west to Pittsburgh, south to Ashburn, then to NJ, then to the server. It's something like 9 hops, but my ping to the server is ~25 right now.
     
    Collapse Signature Expand Signature
    Down Syndrome likes this.
  2. Scrubby Bear

    Scrubby Bear Eodrin
    Hero

    Joined:
    Apr 10, 2016
    Messages:
    2,121
    Likes Received:
    5,834
    Planetside 2 uses a server in VA for their east coast server if I remember right.
     
    Fengor and RootedOak like this.
  3. JEDIMind

    JEDIMind Black Knight
    Wealthy

    Joined:
    Apr 14, 2016
    Messages:
    1,114
    Likes Received:
    1,492
    Have to agree with Scrubby. I ping 130-140 from NV to NY. Chicago I get 60. I have to use battleping in order to play Darkfalll and I'm not the only one... You guys need to drop the whole New York thing. It will be the difference between people staying and leaving.
     
  4. VVolfgang

    VVolfgang Fire Elemental
    Legend

    Joined:
    Aug 8, 2016
    Messages:
    435
    Likes Received:
    204
    Oklahoma

    I like the Chicago Servers.


    Pinging 107.155.107.163 with 32 bytes of data:


    Reply from 107.155.107.163: bytes=32 time=67ms TTL=48
    Reply from 107.155.107.163: bytes=32 time=66ms TTL=48
    Reply from 107.155.107.163: bytes=32 time=67ms TTL=48
    Reply from 107.155.107.163: bytes=32 time=66ms TTL=48

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

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


    Pinging 162.249.170.22 with 32 bytes of data:

    Reply from 162.249.170.22: bytes=32 time=59ms TTL=55
    Reply from 162.249.170.22: bytes=32 time=61ms TTL=55
    Reply from 162.249.170.22: bytes=32 time=60ms TTL=55
    Reply from 162.249.170.22: bytes=32 time=59ms TTL=55

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

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

    Pinging 172.245.41.146 with 32 bytes of data:

    Reply from 172.245.41.146: bytes=32 time=52ms TTL=52
    Reply from 172.245.41.146: bytes=32 time=53ms TTL=52
    Reply from 172.245.41.146: bytes=32 time=54ms TTL=53
    Reply from 172.245.41.146: bytes=32 time=54ms TTL=52

    Ping statistics for 172.245.41.146:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 52ms, Maximum = 54ms, Average = 53ms

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

    Pinging 216.107.152.175 with 32 bytes of data:
    Reply from 216.107.152.175: bytes=32 time=41ms TTL=56
    Reply from 216.107.152.175: bytes=32 time=39ms TTL=56
    Reply from 216.107.152.175: bytes=32 time=39ms TTL=56
    Reply from 216.107.152.175: bytes=32 time=40ms TTL=56

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


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


    Pinging 198.144.182.93 with 32 bytes of data:
    Reply from 198.144.182.93: bytes=32 time=52ms TTL=49
    Reply from 198.144.182.93: bytes=32 time=48ms TTL=49
    Reply from 198.144.182.93: bytes=32 time=49ms TTL=49
    Reply from 198.144.182.93: bytes=32 time=48ms TTL=49

    Ping statistics for 198.144.182.93:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 52ms, Average = 49ms
     
    Collapse Signature Expand Signature
    #64 VVolfgang, Mar 21, 2017
    Last edited: Mar 21, 2017
  5. RootedOak

    RootedOak Oak Lord
    Legend

    Joined:
    Oct 29, 2015
    Messages:
    3,041
    Likes Received:
    4,086
    Pittsburgh, PA
    Xfinity
    Hardwired

    Ping statistics for 107.155.107.163:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 45ms, Average = 23ms

    Tracing route to 107-155-107-163-customer-incero.com [107.155.107.163]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 12 ms 9 ms 9 ms my house
    3 12 ms 9 ms 9 ms te-8-4-ur01.indiana.pa.pitt.comcast.net [68.85.157.109]
    4 17 ms 11 ms 11 ms te-9-1-ur02.ross.pa.pitt.comcast.net [68.86.100.77]
    5 18 ms 19 ms 19 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
    6 15 ms 16 ms 19 ms hu-0-10-0-7-pe04.ashburn.va.ibone.comcast.net [68.86.87.6]
    7 17 ms 19 ms 16 ms 23.30.206.206
    8 22 ms 21 ms 21 ms et-10-1-0.cr4-nyc2.ip4.gtt.net [89.149.130.2]
    9 20 ms 20 ms 22 ms as22773.xe-2-0-7.ar1.nyc3.us.nlayer.net [69.31.95.58]
    10 24 ms 21 ms 24 ms 23.227.177.2
    11 21 ms 31 ms 21 ms 107-155-100-70-customer-incero.com [107.155.100.70]
    12 21 ms 21 ms 24 ms 107-155-107-163-customer-incero.com [107.155.107.163]​

    Ping statistics for 162.249.170.22:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 40ms, Average = 25ms

    Tracing route to 162.249.170.22 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 9 ms 9 ms 9 ms my house
    3 13 ms 9 ms 9 ms te-8-2-ur01.indiana.pa.pitt.comcast.net [68.85.157.105]
    4 13 ms 14 ms 11 ms te-9-1-ur02.ross.pa.pitt.comcast.net [68.86.100.77]
    5 16 ms 16 ms 19 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
    6 17 ms 16 ms 19 ms hu-0-11-0-2-pe04.ashburn.va.ibone.comcast.net [68.86.88.58]
    7 23 ms 21 ms 16 ms ae4.er2.iad10.us.zip.zayo.com [64.125.12.145]
    8 18 ms 19 ms 19 ms ae1.cr2.dca2.us.zip.zayo.com [64.125.20.121]
    9 27 ms 24 ms 24 ms ae27.cs2.dca2.us.eth.zayo.com [64.125.30.248]
    10 28 ms 24 ms 24 ms ae4.cs2.lga5.us.eth.zayo.com [64.125.29.30]
    11 27 ms 24 ms 24 ms ae27.cr2.lga5.us.zip.zayo.com [64.125.30.253]
    12 22 ms 24 ms 24 ms ae3.er4.lga5.us.zip.zayo.com [64.125.31.246]
    13 27 ms 34 ms 24 ms 208.185.141.138.IPYX-080648-006-ZYO.above.net [208.185.141.138]
    14 23 ms 23 ms 24 ms 162.249.170.100
    15 25 ms 24 ms 24 ms 162.249.170.22​

    Ping statistics for 172.245.41.146:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 54ms, Average = 24ms

    Tracing route to lg.ny.colocrossing.com [172.245.41.146]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 8 ms 9 ms 11 ms my house
    3 12 ms 24 ms 9 ms te-6-4-ur01.indiana.pa.pitt.comcast.net [68.85.157.101]
    4 11 ms 14 ms 11 ms te-9-1-ur02.ross.pa.pitt.comcast.net [68.86.100.77]
    5 17 ms 19 ms 19 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
    6 22 ms 24 ms 24 ms be-10102-cr01.newark.nj.ibone.comcast.net [68.86.85.162]
    7 23 ms 24 ms 24 ms be-10203-cr02.newyork.ny.ibone.comcast.net [68.86.85.186]
    8 23 ms 26 ms 24 ms be-10368-pe01.111eighthave.ny.ibone.comcast.net [68.86.84.218]
    9 30 ms 29 ms 34 ms 50.242.150.38
    10 33 ms 31 ms 26 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 24 ms 24 ms 24 ms lg.ny.colocrossing.com [172.245.41.146]
    14 22 ms 26 ms 24 ms lg.ny.colocrossing.com [172.245.41.146]
    15 25 ms 22 ms 27 ms lg.ny.colocrossing.com [172.245.41.146]
    Chi Town

    Ping statistics for 216.107.152.175:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 68ms, Average = 49ms

    Tracing route to s102-cdc603.privatesitelabel.com [216.107.152.175]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 8 ms 9 ms 9 ms my house
    3 12 ms 9 ms 9 ms te-6-2-ur01.indiana.pa.pitt.comcast.net [68.85.157.97]
    4 14 ms 11 ms 11 ms te-9-1-ur02.ross.pa.pitt.comcast.net [68.86.100.77]
    5 21 ms 19 ms 31 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
    6 16 ms 16 ms 19 ms hu-0-10-0-0-pe04.ashburn.va.ibone.comcast.net [68.86.82.214]
    7 16 ms 16 ms 19 ms 23.30.206.206
    8 44 ms 44 ms 44 ms et-1-1-0.cr1-chi1.ip4.gtt.net [89.149.186.54]
    9 40 ms 38 ms 40 ms 427.xe2-0-0.br1.ch2.newcontinuum.net [173.205.36.74]
    10 51 ms 49 ms 49 ms 7-101-79-64.as20278.net [64.79.101.7]
    11 51 ms 49 ms 49 ms 242-2-88-167.reverse-dns.chicago [167.88.2.242]
    12 47 ms 47 ms 50 ms s102-cdc603.privatesitelabel.com [216.107.152.175]​

    Ping statistics for 198.144.182.93:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum = 62ms, Average = 44ms

    Tracing route to lg.chi.colocrossing.com [198.144.182.93]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 11 ms 8 ms 9 ms my house
    3 8 ms 9 ms 9 ms te-6-4-ur01.indiana.pa.pitt.comcast.net [68.85.157.101]
    4 12 ms 11 ms 14 ms te-9-1-ur02.ross.pa.pitt.comcast.net [68.86.100.77]
    5 20 ms 19 ms 19 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
    6 24 ms 24 ms 24 ms be-10102-cr01.newark.nj.ibone.comcast.net [68.86.85.162]
    7 24 ms 24 ms 24 ms be-10203-cr02.newyork.ny.ibone.comcast.net [68.86.85.186]
    8 45 ms 41 ms 46 ms be-10305-cr02.350ecermak.il.ibone.comcast.net [68.86.85.202]
    9 44 ms 41 ms 46 ms be-10563-pe01.350ecermak.il.ibone.comcast.net [68.86.82.158]
    10 40 ms 44 ms 41 ms 50.242.150.34
    11 42 ms 44 ms 41 ms ae4.cr2.ord6.us.scnet.net [204.93.204.87]
    12 44 ms 41 ms 46 ms 72.ae2.ar1.ord6.us.scnet.net [204.93.204.155]
    13 45 ms 41 ms 41 ms as36352.xe-2-1-3.ar1.ord6.us.scnet.net [50.31.151.170]
    14 * * * Request timed out.
    15 48 ms 41 ms 41 ms lg.chi.colocrossing.com [198.144.182.93]​

    Buffalo

    Ping statistics for 198.12.127.26:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 41ms, Average = 34ms

    Tracing route to lg.buf.colocrossing.com [198.12.127.26]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 10 ms 11 ms 9 ms my house
    3 9 ms 9 ms 9 ms te-6-4-ur01.indiana.pa.pitt.comcast.net [68.85.157.101]
    4 9 ms 14 ms 11 ms te-9-1-ur02.ross.pa.pitt.comcast.net [68.86.100.77]
    5 19 ms 19 ms 19 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
    6 19 ms 19 ms 19 ms be-10142-pe01.ashburn.va.ibone.comcast.net [68.86.86.34]
    7 17 ms 19 ms 16 ms ash-b1-link.telia.net [62.115.149.64]
    8 16 ms 19 ms 24 ms ash-bb4-link.telia.net [62.115.123.56]
    9 23 ms 24 ms 24 ms nyk-bb4-link.telia.net [62.115.136.200]
    10 31 ms 36 ms 34 ms buf-b1-link.telia.net [62.115.122.18]
    11 35 ms 31 ms 31 ms colocrossing-ic-314282-buf-b1.c.telia.net [62.115.59.94]
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 36 ms 31 ms 34 ms lg.buf.colocrossing.com [198.12.127.26]​

    Ping statistics for 23.236.154.250:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 46ms, Average = 34ms

    Tracing route to 23.236.154.250 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 10 ms 9 ms 9 ms my house
    3 10 ms 9 ms 9 ms te-6-2-ur01.indiana.pa.pitt.comcast.net [68.85.157.97]
    4 11 ms 11 ms 14 ms te-9-1-ur02.ross.pa.pitt.comcast.net [68.86.100.77]
    5 15 ms 16 ms 16 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
    6 26 ms 16 ms 16 ms be-10142-pe01.ashburn.va.ibone.comcast.net [68.86.86.34]
    7 22 ms 19 ms 19 ms ash-b1-link.telia.net [62.115.149.64]
    8 17 ms 16 ms 19 ms ash-bb4-link.telia.net [80.91.245.67]
    9 24 ms 24 ms 24 ms nyk-bb4-link.telia.net [62.115.136.200]
    10 35 ms 31 ms 31 ms buf-b1-link.telia.net [62.115.141.180]
    11 32 ms 31 ms 34 ms colocrossing-ic-317201-buf-b1.c.telia.net [62.115.146.151]
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 31 ms 34 ms 31 ms x10.smer2.buf1.servermania.com [192.227.179.162]
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 32 ms 30 ms 32 ms 23.236.154.250
    EDIT: Did the tracer routes.
     
    Collapse Signature Expand Signature
    #65 RootedOak, Mar 21, 2017
    Last edited: Mar 21, 2017
  6. Down Syndrome

    Down Syndrome Fire Elemental
    Legend

    Joined:
    Nov 9, 2015
    Messages:
    437
    Likes Received:
    230
    I really think you should check out Ashburn. I get about 25 ping to all of these but an insane number of hops once I get near the servers. Too lazy/don't care enough to paste all the tracerts. The 3rd NYC was the least amount of hops but the least stable ping. so 1 or 2 for me.
     
  7. Circa

    Circa Black Knight
    Legend

    Joined:
    Mar 5, 2016
    Messages:
    1,398
    Likes Received:
    989
    Las Vegas NV
    Cox
    Wired

    Ping Test

    Chicago


    Ping statistics for 216.107.152.175:
    Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 57ms, Maximum = 93ms, Average = 62ms

    Ping statistics for 198.144.182.93:
    Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 74ms, Maximum = 150ms, Average = 79ms

    Buffalo

    Ping statistics for 198.12.127.26:
    Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 92ms, Maximum = 123ms, Average = 97ms

    Ping statistics for 23.236.154.250:
    Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 91ms, Maximum = 129ms, Average = 96ms


    Chicago Tracert

    Tracing route to s102-cdc603.privatesitelabel.com [216.107.152.175]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 8 ms 7 ms 8 ms 10.64.0.1
    3 11 ms 7 ms 7 ms 100.127.1.130
    4 9 ms 9 ms 8 ms 24-234-6-188.ptp.lvcm.net [24.234.6.188]
    5 19 ms 19 ms 19 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
    6 27 ms 28 ms 27 ms 64.38.110.245
    7 28 ms 31 ms 28 ms 66.186.192.61
    8 26 ms 27 ms 27 ms veg-ten9-7-la-ten1-3.bboi.net [66.186.192.22]
    9 102 ms 73 ms 68 ms chi-t1-4-veg-t1-3.bboi.net [64.127.128.190]
    10 61 ms 63 ms 60 ms xe2-0-0.br0.ch2.newcontinuum.net [64.127.129.6]

    11 66 ms 73 ms 61 ms 29-96-79-64.as20278.net [64.79.96.29]
    12 75 ms 63 ms 62 ms 242-2-88-167.reverse-dns.chicago [167.88.2.242]

    13 63 ms 61 ms 61 ms s102-cdc603.privatesitelabel.com [216.107.152.17
    5]

    Trace complete.

    Tracing route to lg.chi.colocrossing.com [198.144.182.93]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 8 ms 7 ms 8 ms 10.64.0.1
    3 8 ms 7 ms 8 ms 100.127.1.130
    4 8 ms 9 ms 9 ms 24-234-6-188.ptp.lvcm.net [24.234.6.188]
    5 8 ms 10 ms 9 ms ae56.bar1.LasVegas1.Level3.net [4.35.34.213]
    6 * * * Request timed out.
    7 14 ms 15 ms 20 ms GTT-level3-2x10G.LosAngels.Level3.net [4.68.62.2
    ]
    8 78 ms 78 ms 78 ms xe-10-0-3.cr8-chi1.ip4.gtt.net [141.136.108.10]

    9 83 ms 78 ms 79 ms servercentral-gw.ip4.gtt.net [173.205.55.138]
    10 * * * Request timed out.
    11 87 ms 93 ms 77 ms lg.chi.colocrossing.com [198.144.182.93]

    Trace complete.

    Buffalo Tracert

    Tracing route to lg.buf.colocrossing.com [198.12.127.26]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 13 ms 7 ms 8 ms 10.64.0.1
    3 7 ms 7 ms 7 ms 100.127.1.130
    4 8 ms 9 ms 8 ms 24-234-6-188.ptp.lvcm.net [24.234.6.188]
    5 10 ms 9 ms 10 ms ae56.bar1.LasVegas1.Level3.net [4.35.34.213]
    6 * * * Request timed out.
    7 24 ms 15 ms 15 ms Telia-level3-60G.LosAngeles1.Level3.net [4.68.73
    .22]
    8 86 ms 85 ms 87 ms nyk-bb4-link.telia.net [62.115.120.246]
    9 99 ms 99 ms 97 ms buf-b1-link.telia.net [62.115.117.166]
    10 98 ms 97 ms 98 ms colocrossing-ic-314282-buf-b1.c.telia.net [62.11
    5.59.94]
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 97 ms 97 ms 99 ms lg.buf.colocrossing.com [198.12.127.26]

    Trace complete.


    Tracing route to 23.236.154.250 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 9 ms 11 ms 7 ms 10.64.0.1
    3 12 ms 8 ms 7 ms 100.127.1.128
    4 8 ms 6 ms 10 ms 24-234-6-24.ptp.lvcm.net [24.234.6.24]
    5 9 ms 8 ms 8 ms ae54.bar2.LasVegas1.Level3.net [205.129.18.109]

    6 * * * Request timed out.
    7 13 ms 13 ms 14 ms Telia-level3-60G.LosAngeles1.Level3.net [4.68.73
    .22]
    8 86 ms 86 ms 86 ms nyk-bb4-link.telia.net [80.91.246.227]
    9 98 ms 95 ms 95 ms buf-b1-link.telia.net [62.115.117.166]
    10 95 ms 95 ms 95 ms colocrossing-ic-314282-buf-b1.c.telia.net [62.11
    5.59.94]
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 95 ms 101 ms 97 ms x30.smer1.buf1.servermania.com [192.3.186.2]
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 97 ms 96 ms 97 ms 23.236.154.250

    Trace complete.

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

    Chicago! Chicago! Chicago!
     
    Fengor likes this.
  8. negocromn

    negocromn Black Knight
    Legend

    Joined:
    Oct 18, 2015
    Messages:
    1,104
    Likes Received:
    1,132
    Alright euros come out of the woodwork (pref with 200 ping to Chigago).

    Me likes NY.
     
    Collapse Signature Expand Signature
    NonFactor likes this.
  9. Oresmacker

    Oresmacker Obsidian Golem
    Supporter

    Joined:
    Aug 30, 2016
    Messages:
    1,680
    Likes Received:
    2,243
    Dallas, Texas or riot!
     
    VVolfgang likes this.
  10. NonFactor

    NonFactor Forest Golem
    Wealthy Affluent Legend

    Joined:
    Jan 23, 2016
    Messages:
    4,913
    Likes Received:
    3,410
    BR power.
     
  11. RootedOak

    RootedOak Oak Lord
    Legend

    Joined:
    Oct 29, 2015
    Messages:
    3,041
    Likes Received:
    4,086
    Updated my post with tracer routes.
     
    Collapse Signature Expand Signature
    Fengor likes this.
  12. Andrew

    Andrew Eodrin
    Staff Member BPG Representative

    Joined:
    Aug 25, 2015
    Messages:
    2,043
    Likes Received:
    4,625
    Every bit helps buddy, the traces especially are valuable and 100 is still a solid ping test.

    Thanks!
    --- Post updated ---
    Cheers!
     
    Collapse Signature Expand Signature
    Myater likes this.
  13. tommeh

    tommeh Dire Zombie
    Contributor Hero

    Joined:
    Oct 14, 2016
    Messages:
    135
    Likes Received:
    111
    South England London
    Wireless
    BT

    Ping statistics for 107.155.107.163:
    Packets: Sent = 81, Received = 80, Lost = 1 (1% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 75ms, Maximum = 83ms, Average = 76ms

    Ping statistics for 162.249.170.22:
    Packets: Sent = 78, Received = 78, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 85ms, Average = 79ms

    Ping statistics for 172.245.41.146:
    Packets: Sent = 80, Received = 80, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 74ms, Maximum = 86ms, Average = 75ms

    Tracing route to 107-155-107-163-customer-incero.com [107.155.107.163]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms bthub [192.168.1.1]
    2 * * * Request timed out.
    3 * 6 ms 6 ms 31.55.187.197
    4 7 ms 7 ms 7 ms 31.55.187.196
    5 7 ms 7 ms 7 ms 195.99.127.14
    6 10 ms 7 ms 7 ms host213-121-193-203.ukcore.bt.net [213.121.193.203]
    7 8 ms 7 ms 7 ms t2c3-et-7-1-0-0.uk-lon1.eu.bt.net [166.49.211.228]
    8 7 ms 7 ms 7 ms 166-49-211-38.eu.bt.net [166.49.211.38]
    9 77 ms 76 ms 76 ms xe-3-2-1.cr4-nyc2.ip4.gtt.net [89.149.134.70]
    10 76 ms 76 ms 76 ms as22773.xe-2-0-7.ar1.nyc3.us.nlayer.net [69.31.95.58]
    11 76 ms 76 ms 76 ms 23.227.177.2
    12 77 ms 76 ms 76 ms 107-155-100-70-customer-incero.com [107.155.100.70]
    13 77 ms 76 ms 77 ms 107-155-107-163-customer-incero.com [107.155.107.163]

    Tracing route to 162.249.170.22 over a maximum of 30 hops

    1 1 ms <1 ms <1 ms bthub [192.168.1.1]
    2 * * * Request timed out.
    3 12 ms 6 ms 6 ms 31.55.187.197
    4 7 ms 7 ms 11 ms 31.55.187.216
    5 7 ms 7 ms 7 ms core1-hu0-7-0-1.southbank.ukcore.bt.net [195.99.127.180]
    6 8 ms 7 ms 7 ms peer1-xe-11-0-1.faraday.ukcore.bt.net [213.121.193.201]
    7 10 ms 13 ms 9 ms t2c4-et-8-1-0-0.uk-lon1.eu.bt.net [166.49.211.248]
    8 8 ms 11 ms 15 ms hu0-1-0-0.ccr22.lon01.atlas.cogentco.com [130.117.14.229]
    9 12 ms 15 ms 15 ms be2869.ccr42.lon13.atlas.cogentco.com [154.54.57.161]
    10 78 ms 78 ms 79 ms be2490.ccr42.jfk02.atlas.cogentco.com [154.54.42.85]
    11 79 ms 79 ms 78 ms be2061.ccr21.jfk05.atlas.cogentco.com [154.54.3.70]
    12 80 ms 79 ms 79 ms be2809.rcr21.b007023-2.jfk05.atlas.cogentco.com [154.54.81.202]
    13 78 ms 78 ms 81 ms 38.88.134.82
    14 78 ms 79 ms 78 ms 162.249.170.100
    15 78 ms 78 ms 77 ms 162.249.170.22

    Tracing route to lg.ny.colocrossing.com [172.245.41.146]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms bthub [192.168.1.1]
    2 * * * Request timed out.
    3 12 ms 9 ms 8 ms 31.55.187.193
    4 8 ms 12 ms 7 ms 31.55.187.212
    5 15 ms 8 ms 10 ms 195.99.127.14
    6 7 ms 7 ms 7 ms host213-121-193-203.ukcore.bt.net [213.121.193.203]
    7 9 ms 8 ms 9 ms t2c3-et-7-3-0-0.uk-lon1.eu.bt.net [166.49.211.230]
    8 74 ms 74 ms 74 ms ixp1-xe-11-3-1-0.us-nyc.eu.bt.net [166.49.208.169]
    9 * * * Request timed out.
    10 75 ms 74 ms 75 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 78 ms 76 ms 75 ms lg.ny.colocrossing.com [172.245.41.146]
    14 77 ms 76 ms 77 ms lg.ny.colocrossing.com [172.245.41.146]
    15 75 ms 75 ms 75 ms lg.ny.colocrossing.com [172.245.41.146]
     
    Nat likes this.
  14. Nat

    Nat Shadow Knight
    Legend

    Joined:
    Mar 12, 2016
    Messages:
    3,796
    Likes Received:
    7,599

    Incoming jelly west coast players.
     
  15. Nate Thegreat

    Nate Thegreat Crypt Guard
    Legend

    Joined:
    Mar 27, 2016
    Messages:
    199
    Likes Received:
    239
    Rough location: Texas
    Internet Service Provider: Spectrum
    Hardwired or wireless computer connection: Hardwired

    107.155.107.163

    Ping test

    Ping statistics for 107.155.107.163:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 73ms, Average = 53ms


    162.249.170.22

    Ping test

    Ping statistics for 162.249.170.22:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss)
    Approximate round trip times in milli-seconds:
    Minimum = 59ms, Maximum = 77ms, Average = 66ms


    172.245.41.146

    Ping test

    Ping statistics for 172.245.41.146:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 77ms, Average = 57ms


    Chicago:

    216.107.152.175

    Ping test:

    Ping statistics for 216.107.152.175:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 54ms, Average = 38ms


    198.144.182.93


    Ping statistics for 198.144.182.93:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 55ms, Average = 43ms


    Buffalo:


    198.12.127.26

    Ping statistics for 198.12.127.26:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 76ms, Average = 61ms


    23.236.154.250

    Ping statistics for 23.236.154.250:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 71ms, Average = 61ms

    tldr: 107 one is bet but chicago is good too but might punish EU too harshly. I vote for keeping it in NY with a good ISP. Also fuck buffalo.
     
    Collapse Signature Expand Signature
  16. Copperfield

    Copperfield Black Knight
    Legend

    Joined:
    Aug 26, 2015
    Messages:
    1,053
    Likes Received:
    588
    this is completly fcking over europe players.. just to give some US players a shorter distance? common man this cant be sollution to the problems

    http://cablemap.info/

    As you can see on the cable map.. NEW York is the best option of europe players.. its the fastest connection to the US.. you can straight from the sea cable to the server.

    Chicago is way to far inlands, it will increase ping by 20% for europe players


    people are complaining here about the server that is not stable or have a some sort of delay.. THIS HAS NOTHING TO DO WITH A PING

    keep the shit in the new york.. and let killrain fix the server problems
    --- Post updated ---
    lol

    ny and chicago are what? 100 miles apart? and your ping doubles..

    your hopping it not good man..
     
  17. Nightmare UDL

    Nightmare UDL Celestial
    Legend

    Joined:
    Oct 12, 2015
    Messages:
    687
    Likes Received:
    789
    ny and chicago are what? 100 miles apart? and your ping doubles..

    Let's listen to this guy lol


    Why can't we look at current accounts purchased? If there are way more EU players than West coast / Australia / orient players then leave it in NY if it's vice Versa move to Chicago.

    Stable Chicago > Ping Spike NY for anyone
     
    #77 Nightmare UDL, Mar 21, 2017
    Last edited: Mar 21, 2017
    Fengor, Circa and SuB ZeRo like this.
  18. Kilset

    Kilset Black Knight
    Hero

    Joined:
    Aug 27, 2015
    Messages:
    1,124
    Likes Received:
    2,377
    The fact you're completely ignoring the fact that Chicago has superior infrastructure is hilarious copper
     
    Collapse Signature Expand Signature
    SuB ZeRo and Circa like this.
  19. Circa

    Circa Black Knight
    Legend

    Joined:
    Mar 5, 2016
    Messages:
    1,398
    Likes Received:
    989
    NY has dog shit servers.
     
    Myater likes this.
  20. pathion

    pathion Gravelord
    Supporter

    Joined:
    Apr 9, 2016
    Messages:
    237
    Likes Received:
    184
    Where do you get this information from? NYC and DC both have more fiber optic capacity than Chicago. Unless you are talking about where physically there are more server farms? Which really has nothing to do with the conversation.

    I was always told servers are located in Chicago for several reasons

    1- its central
    2- low chance of hurricane and natural disaster
    3- Illinois outside of chicago is flat and cheap to build.

    https://cdn2.vox-cdn.com/assets/4465279/backbone_2000.png

    So please educate me?