Re: Gamerail BLOWS in http://www.dslreports.com/forum/r18140991 en Fri, 27 Nov 2009 20:27:05 EDT Fri, 27 Nov 2009 20:27:05 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18142601 EnasYorl :
said by twizlar See Profile :

I'm not talking about the client side of gamerail, only their network and routing. ANY provider that doubles or triples latency is garbage, regardless of if they are using the client or not. There is no reason for pings to be higher to a server in the SAME building with the same available upstream providers. You are missing the entire point, and the possible future implications for server providers.
You are not using GameRails network, as the GameRail Engineer »Re: Gamerail BLOWS told you as well as I. So how can you comment on something you're not even routing across.

Just because a Gamerail Test Server is reachable from the internet doesn't mean your using their custom network to bypass router hops.]]> http://www.dslreports.com/forum/remark,18142601 Mon, 09 Apr 2007 16:04:10 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18142412 Michieru2 : The peering arrangements should be done from one clear shot am I correct?

You are using two different hops at a peering point with one having more congestion than the other and you are stating that Gamerails network is the one with the higher latency if I am understanding you.

Either way if the routing was longer the pipes are most likely dedicated and used specifically for gaming which still provides lower latency even at longer distances.

While a more significant improvement will be if it where a clear shot, that does not seem to be the case here, but in theory if the pipes are not congested with regular traffic then you will still see some benefit but not as much.

I live in FL, and I am routed all the way to Atlanta, GA where my POP is located. My first hop is 30ms in latency due to that distance.
--
The only limits we have are the one's we set ourselves.]]> http://www.dslreports.com/forum/remark,18142412 Mon, 09 Apr 2007 15:29:45 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18142252 jessegr : Seattle is one of the gateways you can connect to.]]> http://www.dslreports.com/forum/remark,18142252 Mon, 09 Apr 2007 15:00:41 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18142145 twizlar : i'm not talking about the client side of gamerail, only their network and routing. ANY provider that doubles or triples latency is garbage, regardless of if they are using the client or not. There is no reason for pings to be higher to a server in the SAME building with the same available upstream providers. You are missing the entire point, and the possible future implications for server providers.
--
AMD Athlon64 4000+ @ 2723mhz - mountaincable.net wireless Intarweb |
Ipods SUCK]]> http://www.dslreports.com/forum/remark,18142145 Mon, 09 Apr 2007 14:42:29 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18141560 EnasYorl :
said by GR_Alchemist See Profile :

Maybe you should use the GameRail client and our network when pinging servers instead of just using the internet.

Yes we are still putting hardware in place and rolling out our network. You will get to do a public for free test of this soon enough.
Seattle is shown on Phase 1. So it will or won't be a gateway city where clients can connect too?

It appears to me it won't from the diagram.

»www.gamerail.com/index.php?famil···,details]]> http://www.dslreports.com/forum/remark,18141560 Mon, 09 Apr 2007 13:00:13 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18141510 liquidgas : Are you using any type of packet prioritization? Can't tell much from ping times now'a days. A ICMP packet might not even get the same route as another packet.]]> http://www.dslreports.com/forum/remark,18141510 Mon, 09 Apr 2007 12:50:09 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18141443 EnasYorl :
said by twizlar See Profile :

I don't think you are understanding me. I'm not using the GameRail client. Those are servers located exclusively on their network which peers directly with the same providers in dallas and yet their routing is completely messed up. The packets should not be routed from dallas to LA to Denver and BACK to dallas when gamerail is peered directly to them. This has nothing to do with the client side and everything to do with their backbone routing and peering arrangements. I used traceroutes from here as an example. IF they were setup properly I should not have a higher ping and more hops to a server located on their network as opposed to one that isn't the packets SHOULD take the best route
You cannot say Gamerail Blows then if your not using Gamerails network via the client. As your issue is with your ISP as your not bypassing hops to take advantage of Gamerail.

Thanks for clarifying to the thread that you are NOT using Gamerail.

Suggested reading material »www.gamerail.com/index.php?famil···,details]]> http://www.dslreports.com/forum/remark,18141443 Mon, 09 Apr 2007 12:34:58 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18141335 GR_Alchemist : Maybe you should use the GameRail client and our network when pinging servers instead of just using the internet.

Yes we are still putting hardware in place and rolling out our network. You will get to do a public for free test of this soon enough.]]> http://www.dslreports.com/forum/remark,18141335 Mon, 09 Apr 2007 12:09:23 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18141275 twizlar : I don't think you are understanding me. I'm not using the GameRail client. Those are servers located exclusively on their network which peers directly with the same providers in dallas and yet their routing is completely messed up. The packets should not be routed from dallas to LA to Denver and BACK to dallas when gamerail is peered directly to them. This has nothing to do with the client side and everything to do with their backbone routing and peering arrangements. I used traceroutes from here as an example. IF they were setup properly I should not have a higher ping and more hops to a server located on their network as opposed to one that isn't the packets SHOULD take the best route
--
AMD Athlon64 4000+ @ 2723mhz - mountaincable.net wireless Intarweb | Ipods SUCK]]> http://www.dslreports.com/forum/remark,18141275 Mon, 09 Apr 2007 11:56:48 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18141160 EnasYorl :
said by twizlar See Profile :

I know however they are peered directly with the same upstream providers in dallas.
What city are you connected too with Gamerail? If it's not the same city your in, then milage can and will vary allot.

Gamespy won't be for everyone when it's 1st released. Only 6 major cities will be available at launch. Then it will expand to 15 cities later.

They only are peering here so far and not all live.

Public Peering Exchange Points
Exchange Point Name ASN IP Address Mbit/sec
AIX 14960 198.32.132.56 1000
Any2 14960 206.223.143.10 1000
Equinix Chicago 14960 206.223.119.42 1000
Equinix Dallas 14960 1000
NYIIX 14960 198.32.160.180 1000
PAIX Palo Alto 14960 Go Live 5/1/07 1000
SIX 14960 198.32.180.72 1000
Private Peering Facilities
Facility Name ASN City Country SONET Ethr ATM
1 Wilshire 14960 Los Angeles US
Bandwidth Exchange Meet Me Room (St Louis) 14960 St. Louis US
Equinix Chicago 14960 Chicago US
NYCC (111 8th MMR) 14960 New York US
TelX Atlanta 14960 Atlanta US
Westin Building Seattle 14960 Seattle US ]]> http://www.dslreports.com/forum/remark,18141160 Mon, 09 Apr 2007 11:36:22 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18141027 twizlar : I know however they are peered directly with the same upstream providers in dallas.
--
AMD Athlon64 4000+ @ 2723mhz - mountaincable.net wireless Intarweb | Ipods SUCK]]> http://www.dslreports.com/forum/remark,18141027 Mon, 09 Apr 2007 11:08:41 EDT Re: Gamerail BLOWS http://www.dslreports.com/forum/remark,18140991 EnasYorl :
said by twizlar See Profile :

Gamerail BLOWS

First IP is in one of gamerails racks in chicago, the 2nd is also in chicago in equinix 
Tracing route to 208.75.25.70 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    17 ms     5 ms     5 ms  10.150.0.1
  3     8 ms     7 ms     8 ms  border.mountaincable.net [24.215.3.129]
  4    21 ms     8 ms    10 ms  ra2sh-ge3-4-14.mt.bigpipeinc.com [66.244.223.237]
  5     9 ms     7 ms     7 ms  rc1sh-ge9-0-6.mt.shawcable.net [66.163.66.49]
  6    20 ms    21 ms    19 ms  rc1hu-pos5-0-0.ny.shawcable.net [66.163.77.154]
  7    24 ms    22 ms    22 ms  64.243.225.142
  8     *        *        *     Request timed out.
  9    42 ms    47 ms    41 ms  208.75.25.70
 
Trace complete.
 
Tracing route to 64.34.240.161 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms     6 ms     6 ms  10.150.0.1
  3     9 ms     8 ms     9 ms  border.mountaincable.net [24.215.3.129]
  4    10 ms     9 ms     6 ms  VLN.Serialx-x-x.GWx.POPx.ALTER.NET [63.115.224.73]
  5    11 ms     7 ms     9 ms  0.so-6-0-2.XT2.TOR2.ALTER.NET [152.63.133.78]
  6    27 ms    27 ms    26 ms  0.so-6-0-0.XL2.CHI13.ALTER.NET [152.63.70.105]
  7    23 ms    27 ms    23 ms  POS7-0.GW1.CHI13.ALTER.NET [152.63.69.181]
  8    24 ms    30 ms    23 ms  bandwidthoptions.net-gw.customer.alter.net [157.130.173.238]
  9    23 ms    37 ms    23 ms  peer1-chi01-ge2-core1-equinix.ord.gowebman.com [69.90.119.10]
 10    24 ms    22 ms    24 ms  209.8.108.22
 11    21 ms    24 ms    23 ms  64.34.240.161
 
Trace complete.

It doubles my ping to chicago servers, and triples it to dallas. When i ping one of their dallas servers from my own dallas box at the planet it routes through L.A > denver > back to dallas.

Their network isn't fully live. If you read the forums on Gamerail.
]]> http://www.dslreports.com/forum/remark,18140991 Mon, 09 Apr 2007 11:01:02 EDT Gamerail BLOWS http://www.dslreports.com/forum/remark,18140714 twizlar : Gamerail BLOWS

First IP is in one of gamerails racks in chicago, the 2nd is also in chicago in equinix 
Tracing route to 208.75.25.70 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    17 ms     5 ms     5 ms  10.150.0.1
  3     8 ms     7 ms     8 ms  border.mountaincable.net [24.215.3.129]
  4    21 ms     8 ms    10 ms  ra2sh-ge3-4-14.mt.bigpipeinc.com [66.244.223.237]
  5     9 ms     7 ms     7 ms  rc1sh-ge9-0-6.mt.shawcable.net [66.163.66.49]
  6    20 ms    21 ms    19 ms  rc1hu-pos5-0-0.ny.shawcable.net [66.163.77.154]
  7    24 ms    22 ms    22 ms  64.243.225.142
  8     *        *        *     Request timed out.
  9    42 ms    47 ms    41 ms  208.75.25.70
 
Trace complete.
 
Tracing route to 64.34.240.161 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms     6 ms     6 ms  10.150.0.1
  3     9 ms     8 ms     9 ms  border.mountaincable.net [24.215.3.129]
  4    10 ms     9 ms     6 ms  VLN.Serialx-x-x.GWx.POPx.ALTER.NET [63.115.224.73]
  5    11 ms     7 ms     9 ms  0.so-6-0-2.XT2.TOR2.ALTER.NET [152.63.133.78]
  6    27 ms    27 ms    26 ms  0.so-6-0-0.XL2.CHI13.ALTER.NET [152.63.70.105]
  7    23 ms    27 ms    23 ms  POS7-0.GW1.CHI13.ALTER.NET [152.63.69.181]
  8    24 ms    30 ms    23 ms  bandwidthoptions.net-gw.customer.alter.net [157.130.173.238]
  9    23 ms    37 ms    23 ms  peer1-chi01-ge2-core1-equinix.ord.gowebman.com [69.90.119.10]
 10    24 ms    22 ms    24 ms  209.8.108.22
 11    21 ms    24 ms    23 ms  64.34.240.161
 
Trace complete.

It doubles my ping to chicago servers, and triples it to dallas. When i ping one of their dallas servers from my own dallas box at the planet it routes through L.A > denver > back to dallas.

--
AMD Athlon64 4000+ @ 2723mhz - mountaincable.net wireless Intarweb | Ipods SUCK]]> http://www.dslreports.com/forum/remark,18140714 Mon, 09 Apr 2007 09:52:15 EDT