dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
11
share rss forum feed

serge87

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

1 edit
reply to Vamp

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

said by Smith6612:

Has anyone tried tracing something on *.tinet.net during the times where other locations show no issues? Those remain problematic well into the morning for me at home.

>tracert 64.34.181.15
Tracing route to badrush.info [64.34.181.15]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     2 ms     2 ms  74.106.*.*
  3     2 ms     2 ms     2 ms  G5-0-6-220.SYRCNY-LCR-02.verizon-gni.net [130.81.179.130]
  4    11 ms    11 ms    10 ms  P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.186]
  5    11 ms    11 ms    11 ms  0.xe-9-1-0.BR1.NYC1.ALTER.NET [152.63.4.241]
  6     *        *        *     Request timed out.
  7    25 ms    26 ms    25 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  8    22 ms    22 ms    22 ms  ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
  9    22 ms    21 ms    21 ms  ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
 10    18 ms    18 ms    18 ms  ae-33-80.car3.Washington1.Level3.net [4.69.149.133]
 11    44 ms    47 ms    59 ms  PEER-1-NETW.car3.Washington1.Level3.net [4.79.169.246]
 12    35 ms    37 ms    37 ms  10ge.xe-1-1-0.wdc-sp225-sbcor-1.peer1.net [216.187.115.126]
 13    35 ms    34 ms    33 ms  10ge-xe-0-0-1.wdc-sp225-sbdis-1.peer1.net [216.187.120.106]
 14    50 ms    55 ms    31 ms  badrush.info [64.34.181.15]
 
Trace complete.
 

That server from the very first post which Vamp had problems with tinet now shows Level3 as the routing path for me. The first hop on Level3 isn't responding or is overloaded.

said by Xtreme2damax:

I don't know what suddenly changed but my ping returned to normal. I am still keeping an eye on everything to see if that changes but for right now I am pinging around 20ms - 30ms to the server like before.

What is your latency currently? It was around 20ms for me earlier but now has jumped up to ~55ms:

|---------------------------------------------------------------------------------- --------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |  101 |  101 |    0 |    0 |    0 |    0 |
|                             74.106.14.1 -    0 |  101 |  101 |    1 |    1 |   29 |    3 |
|G5-0-6-120.SYRCNY-LCR-01.verizon-gni.net -    0 |  101 |  101 |    3 |    3 |    7 |    3 |
|so-2-0-3-0.NY5030-BB-RTR1.verizon-gni.net -   0 |  101 |  101 |   15 |   22 |  156 |   35 |
| xe-9-1-2-0.PHIL-BB-RTR1.verizon-gni.net -    0 |  101 |  101 |   17 |   25 |  110 |   18 |
|           0.xe-5-1-0.XL3.IAD8.ALTER.NET -    0 |  101 |  101 |   22 |   28 |   97 |   36 |
| GigabitEthernet7-0-0.GW8.IAD8.ALTER.NET -    0 |  101 |  101 |   22 |   24 |   29 |   29 |
|                            63.88.105.94 -    0 |  101 |  101 |   26 |   54 |  144 |   44 |
|10gige0-14-0-0.nyktr1.NewYork.opentransit.net 0 |  101 |  101 |   29 |   43 |   66 |   47 |
|               choopa.GW.opentransit.net -    0 |  101 |  101 |   28 |   30 |   36 |   34 |
|                ve67-br1.pnj1.choopa.net -    0 |  101 |  101 |   37 |   48 |   58 |   49 |
|                108.61.92.162.choopa.net -    0 |  101 |  101 |   31 |   43 |   57 |   49 |
|                 108.61.46.50.choopa.net -    0 |  101 |  101 |   29 |   42 |   66 |   41 |
|________________________________________________|______|______|______|______|______|______|