dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
24
share rss forum feed

serge87

join:2009-11-29
Reviews:
·Verizon FiOS

2 edits
reply to Vamp

Re: [Northeast] High pings / bad routing...

said by Smith6612:

While the hop there is apparently to France or owned by a French company, it isn't going to France as latency would be double of what it's doing now.

Most game servers located in France that are pingable are in the 80-100ms roundtrip for me from NY. Try pinging this game server in France: 193.239.123.12 That server is 100% located in France and you can compare that ping to the transit server in the previous traceroute(193.251.241.213), notice the similar latency range. Even better, try doing a trace from your workplace so the test is more accurate.

ping 193.239.123.12    
 
Pinging 193.239.123.12 with 32 bytes of data:
Reply from 193.239.123.12: bytes=32 time=97ms TTL=51
Reply from 193.239.123.12: bytes=32 time=98ms TTL=51
Reply from 193.239.123.12: bytes=32 time=99ms TTL=51
Reply from 193.239.123.12: bytes=32 time=96ms TTL=51
 
Ping statistics for 193.239.123.12:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 96ms, Maximum = 99ms, Average = 97ms
 

tracert 108.61.46.50         
 
Tracing route to 108.61.46.50.choopa.net [108.61.46.50]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms     1 ms     1 ms  74.106.14.1
  3     3 ms     3 ms     3 ms  G5-0-6-120.SYRCNY-LCR-01.verizon-gni.net [130.81.177.130]
  4    15 ms    15 ms    15 ms  so-2-0-3-0.NY5030-BB-RTR1.verizon-gni.net [130.81.28.184]
  5    18 ms    18 ms    18 ms  xe-9-1-2-0.PHIL-BB-RTR1.verizon-gni.net [130.81.23.108]
  6    24 ms    24 ms    24 ms  0.xe-5-1-0.XL3.IAD8.ALTER.NET [152.63.6.9]
  7    24 ms    23 ms    23 ms  GigabitEthernet7-0-0.GW8.IAD8.ALTER.NET [152.63.33.17]
  8    85 ms    72 ms    73 ms  63.88.105.94
  9    97 ms    95 ms    88 ms  tengige0-11-0-0.nyktr1.NewYork.opentransit.net [193.251.243.157]
 10    79 ms    89 ms    79 ms  choopa.GW.opentransit.net [193.251.251.102]
 11    90 ms    94 ms    83 ms  ve67-br1.pnj1.choopa.net [108.61.93.109]
 12    92 ms    92 ms    91 ms  108.61.92.162.choopa.net [108.61.92.162]
 13    78 ms    80 ms    81 ms  108.61.46.50.choopa.net [108.61.46.50]
 
Trace complete.
 

edit: server NOT in France


Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Reviews:
·Verizon Online DSL
·Frontier Communi..

1 edit

Here's the thing though. The reason why I stated it couldn't be going to France was due to the fact that with the way Verizon sends things, it seems you have to tack on at least 10ms for a round trip just to New York. From there, transit tends to be around 80ms from France in back. When you go: Connection > NYC > Peer > France > New York and back in a round trip you've got something that would easily hit 160+ms. Unless it's "turning around" somewhere in the middle of the ocean?

Anyways, here's the pings to the two servers you asked for. New York server is first followed by the server in France.

Pinging 108.61.46.50 with 32 bytes of data:
Reply from 108.61.46.50: bytes=32 time=8ms TTL=57
Reply from 108.61.46.50: bytes=32 time=8ms TTL=57
Reply from 108.61.46.50: bytes=32 time=7ms TTL=57
Reply from 108.61.46.50: bytes=32 time=8ms TTL=57
 
Ping statistics for 108.61.46.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 8ms, Average = 8ms
 

Pinging 193.239.123.12 with 32 bytes of data:
Reply from 193.239.123.12: bytes=32 time=79ms TTL=55
Reply from 193.239.123.12: bytes=32 time=79ms TTL=55
Reply from 193.239.123.12: bytes=32 time=79ms TTL=55
Reply from 193.239.123.12: bytes=32 time=80ms TTL=55
 
Ping statistics for 193.239.123.12:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 79ms, Maximum = 80ms, Average = 79ms
 
 

Traceroute to France server:

Tracing route to 193-239-123-12.oxyd.net [193.239.123.12]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  xxx.xxx.xxx.xxx
  2    <1 ms    <1 ms    <1 ms  xxx.xxx.xxx.xxx
  3    <1 ms    <1 ms    <1 ms  xxx.xxx.xxx.xxx
  4    <1 ms    <1 ms    <1 ms  xxx.xxx.xxx.xxx
  5     8 ms     7 ms     7 ms  xxx.xxx.xxx.xxx
  6     8 ms     7 ms     8 ms  neotelecoms.tienyc.telxgroup.net [206.126.115.24]
  7    78 ms    79 ms    78 ms  83.167.55.87.static.not.updated.as8218.eu [83.167.55.87]
  8    79 ms    80 ms    78 ms  mornay.gw.vlan52.er1.rb.par.neotelecoms.com [83.167.32.58]
  9    80 ms    79 ms    79 ms  mornay.gw.vlan52.er1.rb.par.neotelecoms.com [83.167.32.58]
 10    79 ms    80 ms    80 ms  193-239-123-12.oxyd.net [193.239.123.12]
 
Trace complete.
 

That's the fastest route I can get to there. But hopefully things are well in Verizon land tonight. I won't be able to check at home until late tonight off peak hours.