I have been having extremely slow speeds to my Gaming Clan website and to some game servers due to a hop not responding. It has been happening all week.
I did a tracert and this is what I have:
Tracing route to monksmilitia.com [192.254.225.150]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 8 ms L100.PHLAPA-VFTTP-161.verizon-gni.net [173.49.61.1]
3 11 ms 10 ms 7 ms G0-5-3-7.PHLAPA-LCR-21.verizon-gni.net [130.81.215.160]
4 18 ms 74 ms 6 ms ae0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.178]
5 51 ms 50 ms 83 ms 0.xe-7-1-0.BR1.IAD8.ALTER.NET [152.63.3.85]
6 89 ms 91 ms 90 ms te0-6-0-14.ccr41.iad02.atlas.cogentco.com [154.54.10.225]
7 83 ms 83 ms 84 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170]
8 87 ms 87 ms 86 ms be2154.ccr41.ord01.atlas.cogentco.com [154.54.30.198]
9 89 ms 86 ms 87 ms be2156.ccr21.mci01.atlas.cogentco.com [154.54.6.85]
10 105 ms 106 ms 105 ms be2128.ccr21.den01.atlas.cogentco.com [154.54.25.173]
11 117 ms 118 ms 119 ms be2126.ccr21.slc01.atlas.cogentco.com [154.54.25.66]
12 134 ms 124 ms 124 ms 38.104.174.198
13 * 122 ms * ve15.ar05.prov.acedc.net [199.58.196.66]
14 * * * Request timed out.
15 124 ms 127 ms 127 ms 192.254.225.150
As you can see some of the hops are a little slow but #14 is not responding. It has always been a solid connection until the past week or so. Very hard for me to run a gaming clan when it takes me more than a day to upload/download files to my site which before this took me a couple of minutes.
So there is definately something going on the at that one hop.
Two observations:
First, the fact that a hop on a trace router doesn't respond is not an indication that that hop isn't working. Some servers are just configured not to respond to trace route pings.
And second, hop 14 is clearly out of Verizon's network and thus if it is a problem, the problem isn't Verizon's.
Having said that, the fact that the tracert completes at step 15, and with a pretty reasonable latency, it seems as if your connection to that server is indeed working...at least for tracert packets.
Sorry that's not an answer to your issue but it doesn't seem like you'll be able to get a resolution from Verizon.
I would agree that the hops are slow to respond, but the hop at hop 14 isn't a problem. You're routing over Cogent in at least one path, which as of right now Verizon doesn't seem to be on good terms with due to the whole Netflix fiasco. Also, your trace runs all the way to Salt Lake City, but that should mean you have 60-70ms latency, not nearly double of that.
Clearly a sign of congestion if the latency is only there in the afternoon/evening hours.
Start a new topic or ask questions in the open forum.
