For a good long while (months) we have had similar issues with various Verizon destinations. I observed it only happens when passing through certain geographic regions of the US. Other regions make it through without issue.
This is directly observable and repeatable using Cogent's Looking glass website. Do an IPv4 Trace to 63.59.67.68 using their US-Minneapollis router. It dies. Do an IPv4 Trace to 63.59.67.68 using their US-Los Angeles router. It reaches the destination. I went through a handful of Cogent's looking glass locations and found some that work and some that don't and concluded there must be one or more Verizon routers in a certain set geographic area that are having the problems. Ultimately the issue is not resolved for me but I was able to BGP TE the traffic around the problem areas to facilitate reachability to the impacted destinations. This is obviously a tenuous band-aid. Long story short: please, please, please, someone at Verizon or someone who has the ear of someone at Verizon, please, please, please, look into this. <cue holo recording R2D2 plays of Princess Leia asking for help> -----Original Message----- From: Richard Laager <rlaa...@wiktel.com<mailto:richard%20laager%20%3crlaa...@wiktel.com%3e>> To: nanog@nanog.org<mailto:nanog@nanog.org> Subject: Verizon Business Contact Date: Thu, 08 Feb 2024 13:01:14 -0600 Can someone from Verizon Business please contact me? It appears that your network is losing traffic from Verizon Wireless (e.g. 63.59.39.232, 63.56.37.4, or 63.59.67.68) to me (AS33362, e.g. to 69.89.207.16). Note that 63.59.166.100 -> 69.89.207.16 was successfully (around 2023-11-27). This breaks email between us and it's been MONTHS of VZW getting nowhere. Based on some traceroutes (on 2023-11-27 and again just now), the working ones go through 140.222.234.223 (0.ae10.GW7.CHI13.ALTER.NET) while the broken ones stop at 140.222.234.221 (0.ae9.GW7.CHI13.ALTER.NET).
