<div dir="ltr"><div><a href="http://alter.net">alter.net</a> is just the legacy RDNS for things in AS701 (uunet). Nothing weird there. <br></div><div><br></div><div><a href="https://en.wikipedia.org/wiki/UUNET">https://en.wikipedia.org/wiki/UUNET</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Oct 9, 2021 at 1:46 PM Miles Fidelman <<a href="mailto:mfidelman@meetinghouse.net">mfidelman@meetinghouse.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Any Verizon folks here?<br>
<br>
I've been having some rather weird network issues lately - just reading <br>
email via IMAP, from home. Over a 1gig FIOS connection to a machine in <br>
a nearby Tierpoint data center that has LOTS of good connectivity.<br>
<br>
I just tried some traceroutes, and got some interesting results:<br>
<br>
These originate on a machine connected to a 1gig FIOS feed, and end at a <br>
machine, located in a Tierpoint datacenter, about 10 miles from here.<br>
<br>
traceroute to <a href="http://ntcorp.com" rel="noreferrer" target="_blank">ntcorp.com</a> (207.154.13.58), 64 hops max, 52 byte packets<br>
1 * fios_quantum_gateway (192.168.1.1) 3.530 ms 2.822 ms<br>
2 * * *<br>
3 100.41.27.110 (100.41.27.110) 14.970 ms 5.323 ms 6.306 ms<br>
4 <a href="http://0.csi1.bstnmafr-mse01-bb-su1.alter.net" rel="noreferrer" target="_blank">0.csi1.bstnmafr-mse01-bb-su1.alter.net</a> (140.222.10.32) 11.069 ms <br>
8.477 ms 17.097 ms<br>
5 * * *<br>
6 <a href="http://0.ae1.br1.bos30.alter.net" rel="noreferrer" target="_blank">0.ae1.br1.bos30.alter.net</a> (140.222.236.253) 17.121 ms 19.027 ms<br>
<a href="http://0.ae2.br1.bos30.alter.net" rel="noreferrer" target="_blank">0.ae2.br1.bos30.alter.net</a> (140.222.236.255) 19.795 ms<br>
7 * * *<br>
8 <a href="http://colo4-dalla.bear1.boston1.level3.net" rel="noreferrer" target="_blank">colo4-dalla.bear1.boston1.level3.net</a> (4.53.61.86) 2205.648 ms <br>
8.331 ms 13.161 ms<br>
9 <a href="http://static-33-65-203-66.axsne.net" rel="noreferrer" target="_blank">static-33-65-203-66.axsne.net</a> (66.203.65.33) 16.951 ms 13.791 ms<br>
<a href="http://static-145-65-203-66.axsne.net" rel="noreferrer" target="_blank">static-145-65-203-66.axsne.net</a> (66.203.65.145) 21.503 ms<br>
10 <a href="http://server1.ntcorp.com" rel="noreferrer" target="_blank">server1.ntcorp.com</a> (207.154.13.58) 17.872 ms 15.902 ms 14.415 ms<br>
<br>
Several things jump out:<br>
<br>
1. <a href="http://alter.net" rel="noreferrer" target="_blank">alter.net</a> is not a common path between here & there - usually a lower <br>
grade connection, when other backbones aren't working right<br>
<br>
2. origin - <a href="http://alter.net" rel="noreferrer" target="_blank">alter.net</a> - level.3 - endpoint is just bizarre, one would <br>
think that the regional FIOS network has a direct connection to level.3 <br>
(it also seems kind of odd that the packets are flowing from Acton MA, <br>
to Boston, and back out to Marlboro MA - there's an awful lot of fiber <br>
running along Rt. 495, and the networks are fairly dense around here)<br>
<br>
3. The intermittent, high delays (factor of 10) jump out (also, when <br>
running ping tests, there seem to be intermittent periods of long <br>
sequences of timeouts)<br>
<br>
All in all it's really mucking with both streaming services, and simply <br>
posting emails (SMTP timeouts).<br>
<br>
All of which leads me to wonder if there's something mucked up with <br>
Verizon's routing tables (or a particular network interface).<br>
<br>
Any insights (or fixes) to be had?<br>
<br>
Thanks,<br>
<br>
Miles Fidelman<br>
<br>
<br>
<br>
-- <br>
In theory, there is no difference between theory and practice.<br>
In practice, there is. .... Yogi Berra<br>
<br>
Theory is when you know everything but nothing works.<br>
Practice is when everything works but no one knows why.<br>
In our lab, theory and practice are combined:<br>
nothing works and no one knows why. ... unknown<br>
<br>
</blockquote></div>