<div dir="auto"><div dir="auto"><div>Seems to be only having issues in the US, looking at Globalping:</div><div dir="auto"><a href="https://www.jsdelivr.com/globalping">https://www.jsdelivr.com/globalping</a></div><div><br></div><div data-smartmail="gmail_signature">Kind regards,<br><br>Wieger Bontekoe<br>Principal Site Reliability Engineer<br><a href="mailto:wieger.bontekoe@productsup.com" target="_blank" rel="noreferrer">wieger.bontekoe@productsup.com</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op do 4 apr 2024 19:49 schreef Mark Keymer via Outages <<a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I have customer with Verizon having either DNS resolution issues or <br>
return traffic back to them is not being received. I suspect that the <br>
Verizon DNS resolvers are going though the same path that the return <br>
traffic is going down. I have/am working on contacting my upstreams. The <br>
numbers I have found to call version have failed as I do not have an <br>
account.<br>
<br>
Maybe someone here has some information, or has a way to help?<br>
<br>
two know IP's that I am unable to reach are: 72.83.97.146 and 100.18.11.5<br>
<br>
Sample traceroute from me 208.77.208.1 / AS13438:<br>
<br>
traceroute to 72.83.97.146 (72.83.97.146), 30 hops max, 40 byte packets<br>
1 216.243.28.217 11.431 ms 11.387 ms 11.933 ms<br>
2 174.127.149.137 12.008 ms 11.941 ms 11.902 ms<br>
3 69.174.9.189 11.294 ms 11.293 ms 11.237 ms<br>
4 89.149.130.78 11.126 ms 89.149.130.54 12.343 ms 14.100 ms<br>
5 204.148.146.45 11.284 ms 11.216 ms 11.262 ms<br>
6 * * *<br>
7 * * *<br>
8 * * *<br>
9 * * *<br>
10 * * * (Repeating)<br>
<br>
This does not seem to be isolated to me. One of my upstreams confirmed <br>
they could not ping one of the above IP's and if you check out this <br>
remote IP testing site you can see it doesn't seem to be able to reach <br>
it from the two Seattle ISP's. (You can click "Show" on the line to see <br>
traceroute details)<br>
<br>
<a href="https://ping.pe/72.83.97.146" rel="noreferrer noreferrer noreferrer" target="_blank">https://ping.pe/72.83.97.146</a><br>
<br>
<a href="https://ping.pe/100.18.11.5" rel="noreferrer noreferrer noreferrer" target="_blank">https://ping.pe/100.18.11.5</a><br>
<br>
Thank you to anyone in advance that reviews or looks into this.<br>
<br>
Sincerely,<br>
<br>
-- <br>
Mark Keymer<br>
President<br>
Vivio Technologies<br>
Toll Free: 1-877-448-4846<br>
Local: 1-509-593-4207<br>
<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org" rel="noreferrer noreferrer" target="_blank">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote></div></div>