We have been sourcing new providers over the last month or two in preparation for launch and have whittled it down to 3 choices in the NYC area. We looked into Chicago, Buffalo and a few other areas nearby during this vetting process but the end results were always a substantial increase in latency for European connections and a minor, if any, increase for North American connections. Our goal is to keep ping in game under 150ms for virtually all of Europe while still maintaining a North American based server. About 55% of the interested players that have been to our website/forum in the past year and a half are in North America, 30% from Europe and the rest coming from places like Russia, Brazil and dozens of small amounts in other countries around the world. In order to narrow down between these 3 providers that are providing slightly different setups and prices we would like to get feedback from the community on the network side of them. We have internally (thanks to team members from 9 different countries testing ) vetted these three to all be pretty close in response times and routing but we would like a larger sample size from the community before making the final decision. We are looking for Ping, Traceroute and any other network testing tools (mtr/Winmtr for example) for the following IPs below. For any tests run the importance is on reliability over time. This means that a proper result will be from a hardwired connection (Wireless will add a considerable amount of variance in most cases so hard wired computer/laptop connections are preferred) and run for over a period of time of at least 5-10 minutes. ----------------------------------------------------------------------------------------- Below is an example of a 500 ping command: ping 192.168.100.1 -n 500 This would send 500 pings which would take about 8-9 minutes to run. During the time you are testing please try to not have any larger upload/downloads or streaming happening as it will cause false negatives in the test. For those able and willing to you can run a ping such as: ping 192.168.100.1 -t It will run continually until you press ctrl+c while you are looking at the command window. ----------------------------------------------------------------------------------------- To run a ping test: Click start > Run > type "CMD" > open In newer windows versions you can click start and typically just start typing in CMD, then press enter. In the black command prompt type: ping xxx.xxx.xxx.xxx -n <number>. The larger the number the longer it will take, average is about a second per ping. type ping xxx.xxx.xxx.xxx -t to run it indefinitely until you cancel it with ctrl+c. Right click on the command window, select "mark". This will allow you to now highlight text using the mouse. The text you want to highlight will look like this: Ping statistics for 192.168.100.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms We just need the statistics not the lines of individual pings. ----------------------------------------------------------------------------------------- For traceroutes they are run in the same command window using the command tracert xxx.xxx.xxx.xxx This will display the route your computer takes through the internet to reach the server. Results for this test will look like: Tracing route to google.ca [172.217.2.131] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 12 ms 13 ms 10 ms 69.63.255.102 3 * 11 ms 15 ms 104-195-128-110.cpe.teksavvy.com [104.195.128.110] 4 11 ms 12 ms 13 ms 104-195-128-253.cpe.teksavvy.com [104.195.128.253] 5 12 ms 13 ms 12 ms ae1-2170-bdr01-tor2.teksavvy.com [192.171.59.97] 6 10 ms 10 ms 13 ms ae12-0-bdr01-tor.teksavvy.com [206.248.155.10] 7 13 ms 15 ms 12 ms 72.14.212.134 8 10 ms 9 ms 11 ms 209.85.255.232 9 14 ms 13 ms 15 ms 209.85.250.7 10 14 ms 15 ms 13 ms yyz08s14-in-f131.1e100.net [172.217.2.131] These are the basic tests we'd like to finish the report on each provider so a final decision can be made. As always your guys' feedback is a big factor in our decisions so thanks in advance for taking the time to provide tests, it will benefit you guys so we can get the best provider. ----------------------------------------------------------------------------------------- Here are the final 3 providers we're deciding between: 107.155.107.163 162.249.170.22 172.245.41.146 Here's a few other ones guys: Chicago: 216.107.152.175 198.144.182.93 Buffalo: 198.12.127.26 23.236.154.250 To keep it easy to sort through the data please post replies in the following format: Rough location(city, state/province, country): Internet Service Provider: Hardwired or wireless computer connection: 107.155.107.163 Ping test Trace route 162.249.170.22 Ping test Trace route 172.245.41.146 Ping test Trace route (if you are not comfortable posting this you can email me your results directly: andrewb@bpgstudios.com. The information will be kept private, is just for testing and will be deleted once we've made a decision)
They are all shit I get 17-21 hops on these and they are all TRASH routing im not even going to take the time to link them here 300ms on certain hops I LIVE IN ITHACA NY THATS MIDDLE OF NY AND I GET 50MS TO ALL OF THESE.... Edit: If I go to the hospital or university where they have a good infastructer I get 13-19ms STEADY I come home 5 minutes away 45 is the lowest I can hope for and the performance not just have 45 thats obviously good ping but the actual performance is terrible, double casts all the shit we complain about.....not at the hospital or uni so ....chicago please...coming from a New Yorker...good god this place has the worst routing from this Spectrum swap which got straight SQUASHED and they are getting sued left and right up here and in maine etc because of the terrible infastructure not being able to give the "300mbps" down speeds etc their fucking business class is 60mbps at its highest....I can only get 50mbps if I pay like 120$ a month JUST for internet..not a combo
If you are getting problem pings to so many areas it's more likely your ISP. What ISP you use? Please post data.
The last year I've had Spectrum, since I've swapped I've had the best ping I've ever had to any game/server. For example, I ping 55 to League of Legends Chicago server. Far east coast servers have been a joke since the dawn of internet gaming. The only game where my ping is trash is by my surprise, New Jersey servers that host roa servers.
I have great internet speed, every single game I play has stable low ping. RoA is the only one that is unstable. Definitely not on my end.
I have a little higher than I should in most games being from here like...chicago server I could optimally get like 25-30 I get 45 which is completely fine super stable and that goes all the way to EU I get 100-110 on the DnD server and its super stable but for what the fuck ever reason you try to connect to the NE/E coast while being here it's like your route does a circle triangle right angle bullshit route just to fuck with you
Sent via email with my results. Seems like 2nd was best for me. 3rd one really sucked with timeouts etc. Keep in mind I only had time to run 1 test on each aside from the 3rd. I did 3 tests on it of both because it kept giving me timeouts.
I call BS. As a west coast player the difference between Chicago and NY is 30-40+ms. Its the difference between 80 and 120 ping. Basically enjoyable and high and unstable trash. Please don't spout blatant BS like 'a minor if any increase for NA connections' unless you want to keep looking like a complete tool bag. Thanks. Riots chicago server I can actually get a stable 65ms to. Of the 3 IPS listed only the third one was below 120 for me. 107.155.107.163 The more I want to support this game, the more you guys keep looking like you want it to just be 20 ping east coasters meleeing everyone else down with their 100+ pings. Yay.
Rough location(city, state/province, country): montreal, quebec, canadia Internet Service Provider: maskatel Hardwired or wireless computer connection: hardwired C:\Users\Propriétaire>tracert 107.155.107.163 Détermination de l'itinéraire vers 107-155-107-163-customer-incero.com [107.155. 107.163] avec un maximum de 30 sauts : 1 5 ms 9 ms 3 ms router.asus.com [192.168.1.1] 2 26 ms 19 ms 29 ms c7-67-223-149-1.dynamic.sthy.maskatel.ca [67.223 .149.1] 3 25 ms 29 ms 19 ms adsl-37-240-0-72.static.maskatel.ca [72.0.240.37 ] 4 31 ms 23 ms 24 ms 172.16.254.58 5 17 ms 24 ms 29 ms adsl-121-240-0-72.static.maskatel.ca [72.0.240.1 21] 6 25 ms 29 ms 29 ms ia-piex-gw09-vl1310.vtl.net [207.253.79.205] 7 26 ms 39 ms 34 ms 216.113.126.174 8 23 ms 29 ms 25 ms 216.113.126.222 9 24 ms 29 ms 29 ms if-ae-0-2.tcore1.MTT-Montreal.as6453.net [216.6. 115.89] 10 38 ms 29 ms 29 ms if-ae-5-2.tcore1.W6C-Montreal.as6453.net [64.86. 31.6] 11 22 ms 21 ms 25 ms ae6.mtl10.ip4.gtt.net [173.205.62.37] 12 37 ms 33 ms 49 ms xe-5-3-1.cr4-nyc2.ip4.gtt.net [89.149.128.193] 13 35 ms 39 ms 39 ms as22773.xe-2-0-7.ar1.nyc3.us.nlayer.net [69.31.9 5.58] 14 37 ms 47 ms 35 ms 23.227.177.2 15 44 ms 49 ms 35 ms 107-155-100-70-customer-incero.com [107.155.100. 70] 16 41 ms 49 ms 39 ms 107-155-107-163-customer-incero.com [107.155.107 .163] ---------------------------------------------------------------- C:\Users\Propriétaire>tracert 162.249.170.22 Détermination de l'itinéraire vers 162.249.170.22 avec un maximum de 30 sauts. 1 6 ms 7 ms 2 ms router.asus.com [192.168.1.1] 2 27 ms 34 ms 24 ms c7-67-223-149-1.dynamic.sthy.maskatel.ca [67.223 .149.1] 3 22 ms 19 ms 24 ms adsl-37-240-0-72.static.maskatel.ca [72.0.240.37 ] 4 27 ms 23 ms 36 ms 172.16.254.58 5 19 ms 25 ms 19 ms adsl-121-240-0-72.static.maskatel.ca [72.0.240.1 21] 6 27 ms 29 ms 19 ms ia-piex-gw09-vl1310.vtl.net [207.253.79.205] 7 38 ms 39 ms 29 ms 216.113.126.178 8 42 ms 39 ms 45 ms 216.113.126.102 9 29 ms 34 ms 29 ms above.net [198.32.118.25] 10 33 ms 31 ms 35 ms ae5.cr2.lga5.us.zip.zayo.com [64.125.21.82] 11 32 ms 39 ms 36 ms ae3.er4.lga5.us.zip.zayo.com [64.125.31.246] 12 32 ms 34 ms 34 ms 208.185.141.138.IPYX-080648-006-ZYO.above.net [2 08.185.141.138] 13 30 ms 31 ms 35 ms 162.249.170.100 14 33 ms 29 ms 29 ms 162.249.170.22 ------------------------------------------------------------------------------ C:\Users\Propriétaire>tracert 172.245.41.146 Détermination de l'itinéraire vers lg.ny.colocrossing.com [172.245.41.146] avec un maximum de 30 sauts : 1 4 ms 8 ms <1 ms router.asus.com [192.168.1.1] 2 18 ms 25 ms 18 ms c7-67-223-149-1.dynamic.sthy.maskatel.ca [67.223 .149.1] 3 28 ms 20 ms 32 ms adsl-37-240-0-72.static.maskatel.ca [72.0.240.37 ] 4 20 ms 28 ms 20 ms 172.16.254.58 5 28 ms 29 ms 18 ms adsl-121-240-0-72.static.maskatel.ca [72.0.240.1 21] 6 * * * Délai d'attente de la demande dépassé. 7 * * * Délai d'attente de la demande dépassé. 8 25 ms 18 ms 24 ms 72.0.246.54 9 18 ms 27 ms 71 ms 67.69.228.193 10 40 ms 29 ms 39 ms tcore4-montreal02_1-14-0-0.net.bell.ca [64.230.9 1.20] 11 30 ms 37 ms 31 ms tcore3-newyorkaa_hundredgige0-8-0-0.net.bell.ca [64.230.79.142] 12 38 ms 29 ms 29 ms bx7-newyork83_hundredgige0-6-0-0.net.bell.ca [64 .230.79.89] 13 29 ms 39 ms 29 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157] 14 43 ms 39 ms 36 ms vl23-br2.pnj1.choopa.net [66.55.130.53] 15 * * * Délai d'attente de la demande dépassé. 16 * * * Délai d'attente de la demande dépassé. 17 39 ms 29 ms 29 ms lg.ny.colocrossing.com [172.245.41.146] 18 25 ms 27 ms 31 ms lg.ny.colocrossing.com [172.245.41.146] 19 33 ms 29 ms 39 ms lg.ny.colocrossing.com [172.245.41.146] Itinéraire déterminé.
Ping statistics for 162.249.170.22: Packets: Sent = 4, Received = 4, Lost = 0 (0% los Approximate round trip times in milli-seconds: Minimum = 133ms, Maximum = 138ms, Average = 136ms Ping statistics for 172.245.41.146: Packets: Sent = 4, Received = 4, Lost = 0 (0% los Approximate round trip times in milli-seconds: Minimum = 143ms, Maximum = 155ms, Average = 146ms Ping statistics for 107.155.107.163: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 136ms, Maximum = 141ms, Average = 138ms
Centralia, WA Comcast Wired Ping statistics for 107.155.107.163: Packets: Sent = 500, Received = 500, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 94ms, Maximum = 486ms, Average = 105ms 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 * * * Request timed out. 3 13 ms 11 ms 15 ms et-9-3-rur01.tumwater.wa.seattle.comcast.net [68.86.97.141] 4 10 ms 13 ms 13 ms po-2-rur02.tumwater.wa.seattle.comcast.net [68.86.96.218] 5 18 ms 17 ms 16 ms be-44-ar01.seattle.wa.seattle.comcast.net [69.139.164.22] 6 20 ms 18 ms 18 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165] 7 38 ms 38 ms 38 ms be-10825-cr01.9greatoaks.ca.ibone.comcast.net [68.86.85.198] 8 32 ms 85 ms 43 ms hu-0-12-0-0-pe03.11greatoaks.ca.ibone.comcast.net [68.86.82.66] 9 32 ms 33 ms 35 ms ae12.cr2-sjc1.ip4.gtt.net [173.205.58.169] 10 96 ms 103 ms 97 ms xe-1-1-2.cr4-nyc2.ip4.gtt.net [141.136.105.9] 11 98 ms 99 ms 109 ms as22773.xe-2-0-7.ar1.nyc3.us.nlayer.net [69.31.95.58] 12 99 ms 97 ms 95 ms 23.227.177.2 13 99 ms 98 ms 96 ms 107-155-100-70-customer-incero.com [107.155.100.70] 14 102 ms 108 ms 100 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 = 78ms, Maximum = 408ms, Average = 87ms 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 * * * Request timed out. 3 17 ms 12 ms 13 ms et-9-3-rur01.tumwater.wa.seattle.comcast.net [68.86.97.141] 4 16 ms 18 ms 10 ms po-2-rur02.tumwater.wa.seattle.comcast.net [68.86.96.218] 5 17 ms 18 ms 18 ms be-44-ar01.seattle.wa.seattle.comcast.net [69.139.164.22] 6 102 ms 35 ms 20 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165] 7 19 ms 18 ms 18 ms hu-0-13-0-0-pe04.seattle.wa.ibone.comcast.net [68.86.82.234] 8 15 ms 17 ms 25 ms as6461.seattle.wa.ibone.comcast.net [173.167.56.202] 9 96 ms 83 ms 83 ms 64.125.29.104 10 87 ms 90 ms 85 ms ae2.cs2.ord2.us.eth.zayo.com [64.125.29.29] 11 101 ms 84 ms 84 ms ae3.cs2.lga5.us.eth.zayo.com [64.125.29.212] 12 80 ms 86 ms 90 ms ae27.cr2.lga5.us.zip.zayo.com [64.125.30.253] 13 94 ms 82 ms 83 ms ae3.er4.lga5.us.zip.zayo.com [64.125.31.246] 14 84 ms 80 ms 80 ms 208.185.141.138.IPYX-080648-006-ZYO.above.net [208.185.141.138] 15 80 ms 80 ms 85 ms 162.249.170.100 16 83 ms 83 ms 82 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 = 81ms, Maximum = 322ms, Average = 91ms 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 * * * Request timed out. 3 14 ms 22 ms 15 ms et-9-3-rur01.tumwater.wa.seattle.comcast.net [68.86.97.141] 4 11 ms 18 ms 13 ms po-2-rur02.tumwater.wa.seattle.comcast.net [68.86.96.218] 5 16 ms 18 ms 17 ms be-44-ar01.seattle.wa.seattle.comcast.net [69.139.164.22] 6 19 ms 18 ms 23 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165] 7 44 ms 43 ms 43 ms be-10817-cr02.denver.co.ibone.comcast.net [68.86.84.205] 8 66 ms 68 ms 69 ms be-10517-cr02.350ecermak.il.ibone.comcast.net [68.86.85.169] 9 89 ms 95 ms 85 ms be-10305-cr02.newyork.ny.ibone.comcast.net [68.86.85.201] 10 85 ms 91 ms 85 ms be-10368-pe01.111eighthave.ny.ibone.comcast.net [68.86.84.218] 11 84 ms 89 ms 88 ms 50.242.150.38 12 96 ms 85 ms 88 ms vl23-br2.pnj1.choopa.net [66.55.130.53] 13 * * * Request timed out. 14 * * * Request timed out. 15 83 ms 86 ms 86 ms lg.ny.colocrossing.com [172.245.41.146] 16 86 ms 98 ms 93 ms lg.ny.colocrossing.com [172.245.41.146] 17 86 ms 88 ms 88 ms lg.ny.colocrossing.com [172.245.41.146]
Have you ever pinged the chicago riot server for LoL? I don't have the IP off hand but its insane how good their routing is.
im sure it is, i think it's ridiculous that my ping from hawaii is similar (by 10-20 ping) to someone on the west coast regardless though lol.
Even if I use a VPN it doesn't change much. My routing has to go either north to Seattle or south to a california server, so I get nearly the same additional amount as you do crossing the ocean There isn't a direct shot east from Oregon unfortunately.
chicago is straight east of oregon too ;p --- Post updated --- ya some have great pings, but others have horribad pings.
Ugh, really? You are trying to pick latency numbers that do not even reflect the stability potential of the server over performance? What's disappointing is you say you had the opportunity but just pass it off due to "latency".. but what would Chicago or Dallas really add from NYC, about 15-30ms with optimal routing? Most EU countries ping <150ms to the Midwest already. Typically 120-140. Need I actually remind anyone that 150 stable ms is better than unstable <50, which is how the server seems to be performing now. So why is it being passed off so easily? Surely going a bit off the trail would be more worthwhile than to keep trying something that clearly isn't working. At least you would actually know.
Yeah I would rather have worse ping and stable server than lower ping and still the same complaints people have with 50-100 ping lower than I already have.
Even to chicago my routing still goes through seattle. Its just the nature of the way the fiber cabling is done. Maybe one day we will get a major east heading fiber here, but I doubt it will be anytime soon.
