Hello List, I need help getting in touch with someone helpful at AT&T (NetEng and/or trust & safety/abuse/compliance/security or preferably all the above). Starting on November 6th, customers behind AT&T have been unable to reach our IP address 149.137.136.16 which is the API VIP we use to serve downloads from Backblaze B2 buckets. If you go one up (.17) or one down (.15) no issues. I've tried calling the NOC contact per PeeringDB and they were ultimately unhelpful. Because we do not peer directly with AT&T they will not talk to us. I can confirm the reachability issue via AT&T's own public route server (route-server.ip.att.net) where I can ping 149.137.136.15 and .17 successfully, but cannot ping 149.137.136.16. MTRs from customers seem to show the path dies well before us. Here are a couple of examples that show 149.137.136.15 good and 149.137.136.16 bad: This one is from Michigan: $ mtr -w 149.137.136.15 Password: Start: 2025-11-12T13:39:10-0500 HOST: ip-192-168-0-231.ec2.internal Loss% Snt Last Avg Best Wrst StDev 1.|-- ip-192-168-0-1.ec2.internal 0.0% 10 4.0 2.9 2.5 4.0 0.4 2.|-- ip-192-168-1-254.ec2.internal 0.0% 10 3.3 3.3 2.6 3.5 0.2 3.|-- 108-202-236-1.lightspeed.livnmi.sbcglobal.net 0.0% 10 5.4 5.0 4.2 6.5 0.8 4.|-- 71.151.199.86 0.0% 10 6.5 5.8 4.8 6.9 0.6 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.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 9.|-- ae3.cr12-chi1.ip4.gtt.net 0.0% 10 14.7 14.8 13.7 15.9 0.6 10.|-- ae4.cr3-was1.ip4.gtt.net 0.0% 10 34.7 34.9 34.0 35.4 0.4 11.|-- ip4.gtt.net 0.0% 10 34.7 34.6 33.7 35.7 0.5 12.|-- api005.backblazeb2.com 0.0% 10 34.8 35.1 34.1 37.5 0.9 $ mtr -w 149.137.136.16 Start: 2025-11-12T13:39:54-0500 HOST: ip-192-168-0-231.ec2.internal Loss% Snt Last Avg Best Wrst StDev 1.|-- ip-192-168-0-1.ec2.internal 0.0% 10 2.5 2.8 2.5 3.0 0.1 2.|-- ip-192-168-1-254.ec2.internal 0.0% 10 3.4 3.5 3.0 3.8 0.2 3.|-- 108-202-236-1.lightspeed.livnmi.sbcglobal.net 0.0% 10 4.0 5.3 3.9 8.9 1.6 4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 This one is from East Bay, California: $ mtr -w 149.137.136.15 Start: 2025-11-11T14:54:50-0800 HOST: maureen Loss% Snt Last Avg Best Wrst StDev 1.|-- router.lan 0.0% 10 0.6 0.6 0.4 0.8 0.1 2.|-- 192.168.1.254 0.0% 10 1.6 1.5 1.4 1.7 0.1 3.|-- 99-189-116-1.lightspeed.snmtca.sbcglobal.net 0.0% 10 19.7 19.9 19.6 20.6 0.3 4.|-- 71.148.180.125 0.0% 10 20.7 20.2 20.0 20.7 0.3 5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 6.|-- 32.130.91.83 40.0% 10 23.1 34.2 22.3 91.9 28.3 7.|-- 192.205.32.98 0.0% 10 29.4 24.9 23.1 30.2 2.6 8.|-- ae4.cr3-was1.ip4.gtt.net 0.0% 10 81.9 81.9 81.6 82.5 0.3 9.|-- ip4.gtt.net 0.0% 10 82.0 82.0 81.7 82.5 0.2 10.|-- api005.backblazeb2.com 0.0% 10 82.4 82.1 81.3 82.9 0.4 $ mtr -w 149.137.136.16 Start: 2025-11-11T13:49:14-0800 HOST: maureen Loss% Snt Last Avg Best Wrst StDev 1.|-- router.lan 0.0% 10 0.7 0.7 0.5 0.7 0.1 2.|-- 192.168.1.254 0.0% 10 1.5 1.5 1.4 1.5 0.1 3.|-- 99-189-116-1.lightspeed.snmtca.sbcglobal.net 0.0% 10 20.3 20.1 19.6 20.8 0.3 4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 If there is anybody on this list that can throw me a bone, it would be very much appreciated. -- Anthony Hoppe Sr. Network Engineer ahoppe@backblaze.com Backblaze.com -- This email, including its contents and any attachment(s), may contain confidential and/or proprietary information and is solely for the review and use of the intended recipient(s). If you have received this email in error, please notify the sender and permanently delete this email, its content, and any attachment(s). Any disclosure, copying, or taking of any action in reliance on an email received in error is strictly prohibited.