my routing is dropping packets to a sight i use all day long. i didn't have this issue with charter, and when i use a vpn to any city outlet nearby the same route works perfectly.
ignore hop 4-5 verizon routers which simply ignored ping requests.
the problem is mostly with the hop 10-12, i also notified yahoo.com
Tracing route to fd-geoycpi-uno-deluxe.gycpi.b.yahoodns.net [22.214.171.124]
over a maximum of 30 hops:
1 7 ms <1 ms <1 ms 192.168.0.1
2 6 ms 10 ms 10 ms lo0-100.NYCMNY-VFTTP-394.verizon-gni.net [72.80.
3 5 ms 7 ms 11 ms B3394.NYCMNY-LCR-22.verizon-gni.net [100.41.132.
4 * * * Request timed out.
5 * * * Request timed out.
6 8 ms 9 ms 9 ms 0.ae2.GW10.EWR6.ALTER.NET [126.96.36.199]
7 4 ms 9 ms 9 ms 188.8.131.52
8 13 ms 9 ms 9 ms nyk-bb3-link.telia.net [184.108.40.206]
9 14 ms 9 ms 9 ms nyk-b6-link.telia.net [220.127.116.11]
10 9 ms 9 ms 9 ms yahoo-ic-314774-nyk-b6.c.telia.net [18.104.22.168]
11 12 ms 8 ms 9 ms et34.bas4-1-edg.nya.yahoo.com [22.214.171.124]
12 5 ms 9 ms 9 ms et29.usw1-1-edg.nya.yahoo.com [126.96.36.199]
13 5 ms 9 ms 9 ms e2.ycpi.vip.nya.yahoo.com [188.8.131.52]
Strange my tracert has the same 4-5 unknown.
traceroute to oob-media-router-rc1.prod.media.wg1.b.yahoo.com (184.108.40.206) , 5 relative hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 2.794 ms 1011.587 ms 1019.385 ms
2 220.127.116.11 (18.104.22.168) 9.081 ms 14.853 ms 19.092 ms
3 22.214.171.124 (126.96.36.199) 7.451 ms 110.413 ms 114.827 ms
4 * * *
5 * * *
6 0.ae1.gw10.ewr6.alter.net (188.8.131.52) 10.454 ms 57.864 ms 60.175 ms
7 184.108.40.206 (220.127.116.11) 13.828 ms 1030.669 ms 1046.282 ms
8 nyk-bb4-link.telia.net (18.104.22.168) 18.691 ms 98.250 ms 102.894 ms
9 buf-b1-link.telia.net (22.214.171.124) 20.476 ms 195.576 ms 199.978 ms
10 yahoo-ic-315726-buf-b1.c.telia.net (126.96.36.199) 23.185 ms 27.404 ms 31.615 ms
11 unknown-216-115-101-x.yahoo.com (188.8.131.52) 22.846 ms 62.214 ms 65.652 ms
12 unknown-72-30-223-x.yahoo.com (184.108.40.206) 22.774 ms 62.449 ms 71.628 ms
13 unknown-74-6-122-x.yahoo.com (220.127.116.11) 22.106 ms 57.926 ms 60.065 ms
14 po7-fab2-1-gdc.bf1.yahoo.com (18.104.22.168) 23.672 ms 28.198 ms 37.230 ms
15 po-10.bas2-11-prd.bf1.yahoo.com (22.214.171.124) 23.995 ms 92.667 ms 94.762 ms
16 media-router-rc1.prod.media.vip.bf1.yahoo.com (126.96.36.199) 23.798 ms * *
17 media-router-rc1.prod.media.vip.bf1.yahoo.com (188.8.131.52) 16.426 ms * *
18 media-router-rc1.prod.media.vip.bf1.yahoo.com (184.108.40.206) 15.206 ms
Don't see any timeouts on hops 10-12.
WHy do you thing there is a packet drop issue there?
Anfd without looking it up, are those hops even on Verizon network?
the problem is intermittant so a msdos tracert isn't helpful.
this tool may do a better job displaying the problem.
since yahoo belongs to verizon as of march 2017
you'd think they would do a better job of routing it
again, ignore hop 4-5, as it's simply rejecting ping packets.
the real packet loss problem appears to start from hop 8,
but i suspect it's really 10-12 triggerring the problem upstream.
there is no other activity on this fios besides this ping test,
and it's 1am est, so it can't be congestion...
thus far nobody answered my original question.
how do you get VERIZON to recognize and remedy routing problems.
this specific problem is immaterial.
years ago back when i was a business customer with a T1 line,
i could call support with this evidence and they would investigate the CLEC.
now as a residential consumer, I have no idea how best to pursue this
I tweeted this link to @verizonsupport and @YahooCare in hopes someone on their social media team will bump my complaint up to tier3 networking - wish me luck
Remember you are asking peers here.
I am not sure I see anything exciting in any of the reports you posted. Such respons time are typical and well below what some people, not reporting problems, see.
So I just did 100 pings of size 1000 bytes to finance.yahoo.com.
Got 100% success rate with average time of 17ms.
Sounds pretty clean to me.
So tell me what routing problem you beleive needs to be solved?
thanks, but your effort was worthless without seeing your tracert so we can divine what intermediate router is in MY way (not yours) that's causing all these packet errors.
To answer the topic question immediately, it might be worth considering that Yahoo was just recently purchased by Verizon. Right now you're routing through Telia to reach Yahoo services. A "fix" in the routing might just be connecting Verizon's network directly to Yahoo's at the Internet Exchanges, which will take time of course if such a plan is in place. Just like how AOL (which is also owned by Verizon) directly connects up to the Verizon backbone which can be seen in a traceroute.
Other than that, I've noticed that Yahoo at times, likes to stop responding to pings. If I ping them more than 20 times, they tend to just stop responding, and stay like that for a long time, despite what I'm pinging loading up something like their homepage otherwise. So that's also some food for thought. I can't coorelate as to when or why they do that.
Is the packet loss affecting the ability to reach Yahoo services? I don't know if they still offer anything real time since Yahoo Games closed down and Yahoo Messenger was "updated" to lose it's voice calling abilities.
I'm happy to report after several weeks complaining to yahoo, telia and verizon, they finally took that failing router offline (see hop 😎 and it's replacement is working without a hickup. of course i have no idea if my feedback over this mattered at all because none of them ever acknoledged my forum posts, tweets and emails, but at least we have hope that intermittant problems today, can become consistant features tomorrow