[skimanwhite]

No description provided.

[skimanwhite]

Adds Latigo LLC's mirror in Tuscaloosa, Alabama (AS19684).

• HTTPS: https://mirror.latigo.net/almalinux/
• HTTP: http://mirror.latigo.net/almalinux/
• rsync: rsync://mirror.latigo.net/almalinux
• Carries AlmaLinux 8, 9 and 10 (BaseOS, AppStream, CRB, extras, plus), synced every 6 hours from the official rsync tier
• 68 TB storage, 10 Gbps uplink, single host in Tuscaloosa, Alabama, with monitoring and email alerting
• Health endpoint: https://mirror.latigo.net/api/status
• Contact: cory@latigo.net (abuse: abuse@latigo.net)

Verified serving repomd.xml for 8/9/10 on both BaseOS and AppStream. Happy to adjust update_frequency, the rsync module, or the geolocation fields if anything does not match your expectations.

[jonathanspw]

Thanks for the mirror! I've been trying to find us a mirror in Alabama for quite some time :)

[jonathanspw]

It would be great if you'd sync every 3 hours - that's our suggested value, but if you can't 6h is perfectly acceptable.

[jonathanspw]

The folder path without a trailing / throws a 404 which is causing the mirrorlist to flag the mirror as broken.

jonathan@jon-laptop:~$ curl -I https://mirror.latigo.net/almalinux/
HTTP/2 200 
server: nginx
date: Sat, 07 Nov 2026 18:39:57 GMT
content-type: text/html

jonathan@jon-laptop:~$ curl -I https://mirror.latigo.net/almalinux
HTTP/2 404 
server: nginx
date: Sat, 07 Nov 2026 18:39:59 GMT
content-type: text/html
content-length: 146

[skimanwhite]

Thanks Jonathan, and glad Alabama finally shows up on your map. Both points are handled: - The trailing-slash 404 is fixed: https://mirror.latigo.net/almalinux now 301s to /almalinux/. That turned out to be an nginx alias quirk affecting every tree we serve, not just AlmaLinux, so it is corrected for all of them (verified across ubuntu, debian, rocky, almalinux, alpine, archlinux, fedora, opensuse, kernel, apache, mozilla, gnu, cran, ctan, freebsd, kali, mikrotik). - We have moved AlmaLinux to a 3-hour sync cadence as you suggested. Reverse DNS (ip-162-254-225-154.rev.ogital.net) and IPinfo both already resolve to Tuscaloosa, Alabama on AS19684, so the geolocation should score correctly. If the crawler flags anything else, ping me here and I will fix it the same day.

…

-- Cory White Latigo LLC, AS19684 ***@***.***

[jonathanspw]

Looks good now.

Something I did notice, however, is a bit odd routing that you may want to investigate. I'm in the Birmingham area and doing some basic testing from a Windstream/Uniti connection my traffic is bouncing from Birmingham area to Atlanta, which I expect honestly, but then to Nashville, back to Atlanta, before ultimately landing in Tuscaloosa.

traceroute to mirror.latigo.net (162.254.225.154), 30 hops max, 60 byte packets
 1  jon-home (172.19.224.1)  0.154 ms  1013.932 ms  1013.928 ms
 2  * OPNsense.localdomain (192.168.50.1)  0.364 ms  0.354 ms
 3  h1.52.55.139.dynamic.ip.windstream.net (139.55.52.1)  7.193 ms  7.184 ms  7.174 ms
 4  ae4-0.agr04.cmrc01-ga.us.uniti.net (40.138.82.192)  7.061 ms * ae4-0.agr03.cmrc01-ga.us.uniti.net (40.136.117.254)  7.041 ms
 5  * * *
 6  * * nash-b2-link.ip.twelve99.net (62.115.58.252)  17.802 ms
 7  nash-bb1-link.ip.twelve99.net (62.115.137.56)  18.380 ms  18.369 ms  18.505 ms
 8  atl-bb1-link.ip.twelve99.net (62.115.137.54)  16.401 ms nash-bb1-link.ip.twelve99.net (62.115.137.56)  18.203 ms atl-bb1-link.ip.twelve99.net (62.115.137.54)  16.192 ms
 9  atl-b1-link.ip.twelve99.net (62.115.113.9)  16.555 ms  16.481 ms  16.536 ms
10  atl-b1-link.ip.twelve99.net (62.115.113.9)  16.759 ms  16.269 ms  14.712 ms
11  ip-69-67-166-71.rev.ogital.net (69.67.166.71)  16.779 ms 209.170.89.234 (209.170.89.234)  31.791 ms ip-69-67-166-71.rev.ogital.net (69.67.166.71)  17.243 ms
12  ip-69-67-166-71.rev.ogital.net (69.67.166.71)  14.977 ms ip-69-67-166-80.rev.ogital.net (69.67.166.80)  16.952 ms  16.937 ms
13  ip-69-67-166-40.rev.ogital.net (69.67.166.40)  17.374 ms  16.786 ms ip-69-67-166-80.rev.ogital.net (69.67.166.80)  16.621 ms
14  ip-69-67-166-40.rev.ogital.net (69.67.166.40)  15.297 ms  15.543 ms ip-69-67-166-33.rev.ogital.net (69.67.166.33)  22.675 ms
15  ip-162-254-225-16.rev.ogital.net (162.254.225.16)  23.214 ms ip-69-67-166-33.rev.ogital.net (69.67.166.33)  20.985 ms  22.643 ms
16  ip-162-254-225-41.rev.ogital.net (162.254.225.41)  22.675 ms  23.351 ms  23.341 ms
17  ip-162-254-225-41.rev.ogital.net (162.254.225.41)  22.643 ms ip-162-254-225-38.rev.ogital.net (162.254.225.38)  22.876 ms  22.865 ms
18  ip-162-254-225-38.rev.ogital.net (162.254.225.38)  22.853 ms ip-162-254-225-19.rev.ogital.net (162.254.225.19)  22.259 ms ip-162-254-225-38.rev.ogital.net (162.254.225.38)  22.832 ms
19  ip-162-254-225-19.rev.ogital.net (162.254.225.19)  22.239 ms ip-162-254-225-7.rev.ogital.net (162.254.225.7)  21.789 ms  22.047 ms
20  * ip-162-254-225-7.rev.ogital.net (162.254.225.7)  22.062 ms  20.464 ms

[skimanwhite]

Thanks for merging and for the testing, much appreciated. We sync every 3 hours as you suggested, and the trailing-slash 404 is fixed. On the routing: from your traceroute, Uniti hands your traffic to Arelion (Telia) in Nashville, and Arelion backhauls it to Atlanta, where it enters our network (about 16 ms) and crosses our backbone to Tuscaloosa. That detour happens on the Uniti-to-Arelion handoff, before it reaches us, so it isn't something we control, and the extra latency is small. Thanks for flagging it.