dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
6
share rss forum feed

Xtreme2damax

join:2007-03-21
Port Byron, NY

1 edit
reply to Vamp

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

So it's a Fios issue and not a problem with the server I am playing on?

How do I fix this? I'm not sure if calling Verizon will net any improvement and I might waste my time calling only for them to claim it's not their issue. I keep posting and bumping the thread in the Verizon Direct section, it's been a week and still no response. Plus I don't want to go through the steps of unplugging and rebooting the router and ont or have a tech come out since I know it isn't an issue on my end.


serge87

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

2 edits

said by Xtreme2damax:

So it's a Fios issue and not a problem with the server I am playing on?

How do I fix this? I'm not sure if calling Verizon will net any improvement and I might waste my time calling only for them to claim it's not their issue. I keep posting and bumping the thread in the Verizon Direct section, it's been a week and still no response. Plus I don't want to go through the steps of unplugging and rebooting the router and ont or have a tech come out since I know it isn't an issue on my end.

At second glance I'm not 100% sure about the 14th hop being in France, even though many signs point to it. However, Verizon's edge router(63.88.105.94) seems to be overloaded and has pretty high latency if its location in Delaware is correct. From NY it's pinging in the 90ms range, I don't even think LA servers have that high of a roundtrip to NY.

|---------------------------------------------------------------------------------- --------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    1 | 1129 | 1127 |    0 |    0 |    0 |    0 |
|                             74.106.14.1 -    0 | 1136 | 1136 |    1 |    9 | 1398 |    1 |
|G5-0-6-120.SYRCNY-LCR-01.verizon-gni.net -    0 | 1137 | 1137 |    3 |    3 |    7 |    3 |
|so-2-0-3-0.NY5030-BB-RTR1.verizon-gni.net -   1 | 1134 | 1132 |    0 |   23 |  187 |   15 |
|           0.xe-5-0-1.XT1.NYC9.ALTER.NET -    1 | 1133 | 1132 |   15 |   18 |   97 |   15 |
|           0.xe-3-0-3.XL3.IAD8.ALTER.NET -    1 | 1121 | 1117 |   21 |   25 |  114 |   22 |
| GigabitEthernet6-0-0.GW8.IAD8.ALTER.NET -    1 | 1133 | 1132 |   22 |   25 |   33 |   23 |
|                            63.88.105.94 -    1 | 1133 | 1132 |   22 |   85 |  152 |   24 |
|________________________________________________|______|______|______|______|______|______|
 

Up until to that router, everything is smooth sailing in the 20ms range. I would go after Verizon about it but I know the pain that is necessary to get anywhere with them.

Edit:

I just ran a trace route to that game server and out of the blue got these results:

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.*.*
  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    23 ms    23 ms    22 ms  GigabitEthernet5-0-0.GW8.IAD8.ALTER.NET [152.63.33.97]
  8    25 ms    25 ms    25 ms  63.88.105.94
  9    35 ms    36 ms    34 ms  tengige0-11-0-0.nyktr1.NewYork.opentransit.net [193.251.243.157]
 10    35 ms    29 ms    29 ms  choopa.GW.opentransit.net [193.251.251.102]
 11    30 ms    29 ms    29 ms  ve67-br1.pnj1.choopa.net [108.61.93.109]
 12    30 ms    30 ms    30 ms  108.61.92.162.choopa.net [108.61.92.162]
 13    30 ms    31 ms    30 ms  108.61.46.50.choopa.net [108.61.46.50]
 
Trace complete.
 

Xtreme, run a trace to that server and post your results.

Xtreme2damax

join:2007-03-21
Port Byron, NY

2 edits

C:\Users\Kenneth>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  Wireless_Broadband_Router.home [192.168.1.1]
  2     4 ms     3 ms     4 ms  L100.SYRCNY-VFTTP-06.verizon-gni.net [72.90.76.1
]
  3     4 ms     5 ms     4 ms  G5-0-2-216.SYRCNY-LCR-02.verizon-gni.net [130.81
.179.122]
  4    12 ms    12 ms    12 ms  P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.1
86]
  5    82 ms    16 ms    15 ms  xe-9-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
23.57]
  6    21 ms    34 ms    62 ms  0.xe-3-0-2.XL4.IAD8.ALTER.NET [152.63.3.57]
  7    28 ms    28 ms    28 ms  GigabitEthernet5-0-0.GW8.IAD8.ALTER.NET [152.63.
33.97]
  8    29 ms    28 ms    37 ms  63.88.105.94
  9    37 ms    44 ms    36 ms  tengige0-11-0-0.nyktr1.NewYork.opentransit.net [
193.251.243.157]
 10    38 ms    24 ms    25 ms  choopa.GW.opentransit.net [193.251.251.102]
 11    32 ms    25 ms    24 ms  ve67-br1.pnj1.choopa.net [108.61.93.109]
 12    25 ms    25 ms    25 ms  108.61.92.162.choopa.net [108.61.92.162]
 13    20 ms    20 ms    24 ms  108.61.46.50.choopa.net [108.61.46.50]
 
Trace complete.
 
C:\Users\Kenneth>
 

This is what I get now. It's seems to be an on and off issue. If I run into issues again which I likely will in a short while I'll post an update.

guppy_fish
Premium
join:2003-12-09
Lakeland, FL
kudos:1
reply to Xtreme2damax

NM, I replied to a post from page 4, not realizing there was a full page 5