Networks not reachable from FIOS as if there's no route

[zeng]

Networks not reachable from FIOS as if there's no route

Can Verizon network team take a look at this?

root# for i in 8.8.8.8 121.51.175.17 121.51.22.64 182.254.52.163 182.254.60.11; do mtr -ur $i; done
HOST: Loss% Snt Last Avg Best Wrst StDev
1.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
2.|-- 100.41.26.128 0.0% 10 10.9 11.7 8.7 14.3 1.7
3.|-- 140.222.10.38 0.0% 10 16.2 15.8 14.0 18.4 1.3
4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 140.222.227.25 0.0% 10 16.9 16.4 14.8 22.4 2.4
7.|-- 72.14.208.130 0.0% 10 15.6 15.4 12.6 16.8 1.4
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
HOST: Loss% Snt Last Avg Best Wrst StDev
1.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
4.|-- 100.41.26.128 90.0% 10 9.2 9.2 9.2 9.2 0.0
HOST: Loss% Snt Last Avg Best Wrst StDev
1.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
2.|-- 100.41.26.126 90.0% 10 11.4 11.4 11.4 11.4 0.0
HOST: Loss% Snt Last Avg Best Wrst StDev
1.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
4.|-- 100.41.26.126 90.0% 10 12.0 12.0 12.0 12.0 0.0
HOST: Loss% Snt Last Avg Best Wrst StDev
1.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 100.41.26.128 80.0% 10 14.7 12.0 9.3 14.7 3.8

[Cang_Household]

Hello. This is largely a customer to customer forum.

From your mtr output, the traceroute and ping seem normal. Some of routers on Verizon network and peer networks are not pingable, hence the * * * and 100% failed.

Are you trying to access a specific IP address and it is not routable? Or, a domain name does not resolute into an IP address? DNS servers on Verizon network may take some time to populate DNS entries.

[gs0b]

Welcome to the forums.  You're talking to other users here.  Your message will not be seen by Verizon's network team.  If you want to reach them, you need to contact Verizon's support team through chat or phone.

That said, I don't see a problem in your traces.  Some nodes outside of the Verizon network are not responding to pings during a trace.  That's not unusual for some network nodes. 

I am a bit confused by your traces, as I don't see your gateway router as the first hop.  Could your system have a configuration issue?

For comparison, here's a trace I did from a WSL Ubuntu system to Google's DNS (personal info REDACTED):

$ mtr -ur 8.8.8.8
Start: 2021-07-02T09:36:33-0400
HOST: <REDACTED> Loss% Snt Last Avg Best Wrst StDev
1.|-- <REDACTED> 0.0% 10 0.2 0.5 0.2 0.9 0.3
2.|-- Fios_Quantum_Gateway.fios 0.0% 10 1.2 1.3 0.7 1.7 0.3
3.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
4.|-- b3358.phlapa-lcr-22.veriz 0.0% 10 9.1 7.1 3.5 9.4 1.7
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 0.et-9-1-2.gw15.nyc1.alte 0.0% 10 9.4 8.3 7.2 9.4 0.9
8.|-- 72.14.208.130 0.0% 10 6.7 7.1 6.1 8.6 1.1
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

[smith6612]

In case it's helpful, Verizon has a Looking Glass server you can use. This can help rule out something in their backbone, versus something that might be closer to your home, such as on the "Verizon Online" side or your router: https://enterprise.verizon.com/why-verizon/looking-glass/

FWIW, ICMP Traceroute is broke on FiOS the last I checked. So ensure you're using UDP Traceroute and your network is allowing UDP traffic to pass.

[zeng]

Yeah the -u flag in mtr says it's UDP

[zeng]

Are you on FIOS as well and could you post your traceroute to IPs listed above other than 8.8.8.8?

[zeng]

Yeah it's this IOS game that I'm playing. It reaches out to those IPs to fetch advertise video. Somehow it fails on FIOS but works perfectly from other cloud VPS and my ATT LTE network.

[gs0b]

Yes, I'm on fios.  It would be kind of pointless to participate in a fios forum and post traceroutes if I wasn't.  🙂

Have you "pinged" all the IPs you are concerned about?  If you can ping them, that means you can reach them.  The traceroutes that have some blanks in the middle are simply nodes that don't reply to pings.  No big deal.

I tried pinging a few of the IPs on your list, but they don't respond.  If you get similar results, then you probably have an issue to ask Verizon support about.

[zeng]

Those IPs do not respond to ping from FIOS home network, but they do when I test from Oracle cloud VM. And the traceroute also points to potential blackhole/filtering right beyond hops 100.41.26.126/100.41.26.128. 

The blanks are not a concern. It's just that when traceroute to 8.8.8.8 completes successfully it does indicate that it's unlikely that all the hops beyond 100.41.26.126/100.41.26.128 would not generate ICMP in response to TTL expiration, and when it does happen blackhole/filtering would be my guess at the moment.

[gs0b]

Reasonable hypothesis.  But since nobody here works for Verizon or can talk to their network team, we can't do anything about it.  If you want to ask them about it, you need to contact their support team.  They may escalate to the network team, once they understand the issue.  The best way to reach them for issues like this is to use their social media support team.  To get to them, tweet @VerizonSupport or pop over to https://www.dslreports.com/forum/vzdirect create and account and post.  Both methods should result in a link to a private chat where they will collect the details.

You can also try the standard support chat.  But whatever you do, don't waste your time with phone support.