So, half my websites have been taking forever to load and I finally did a tracert to find out why... Repeatedly I get the same results... Timeouts on two main hops...
Verizon???
Tracing route to google.com [216.58.217.110]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
2 8 ms 9 ms 8 ms lo0-100.PITBPA-VFTTP-307.verizon-gni.net [72.95.128.1]
3 9 ms 11 ms 6 ms B3307.PITBPA-LCR-22.verizon-gni.net [130.81.171.6]
4 * * * Request timed out.
5 * * * Request timed out.
6 19 ms 21 ms 21 ms 0.ae14.GW9.IAD8.ALTER.NET [140.222.236.143]
7 23 ms 19 ms 19 ms pool-96-236-104-66.burl.east.verizon.net [96.236.104.66]
8 20 ms 19 ms 18 ms 108.170.246.33
9 20 ms 18 ms 19 ms 66.249.95.21
10 19 ms 21 ms 21 ms iad23s42-in-f110.1e100.net [216.58.217.110]
It would seem the problem is after Verizon.gni.net
between that and alter.net so it is not Verizon as I can see from your tracert.
my question would be what hops are missing? There are two unknowns. Is it the handoff from Verizon to another Verizon hop? Or another peering site.
very strange I used tracert from New York and no time outs or delays.
hop 4-5 are verizon routers simply ignoring ping packets.
i know it's stupid of them to do so, but there you have it.
i suggest you adjust your router's QoS 5% under the speeds you pay for.
that may lower the down:up latency and improve site load responsiveness.
As I stated in my reply "the 4-5 are unknowns" you cannot tell from that tracert what the connection is.
And Quality of Service is not always set on due to it having a lagging effect on the routers speeds. Most folks just keep it set to the default position of "off"
Nothing in that trace looks bad. Very respectable response times. And yes some servers are set to either not respond or repond a lower priority which times out.
I would guess the unresponding servers are also Verizon, (alter.net is also Verizon).
Start a new topic or ask questions in the open forum.
