network unreachable for ppa.launchpad.net

[milos]

Hello,
I'm one of the developers on the Bitbucket pipelines where we provide CICD in the cloud for our customers. Recently we started seeing reports that connections to ubuntu.com and ppa.launchpad.net fail with 'network unreachable'. It's been on and off for a few days now. it appears to work sometimes and then it breaks again. There is no mention of incident on your side AFAIK. Is there specificly something you are doing to block our traffic?
example public IP address of our kubernetes is:curl ifconfig.co - > 52.202.195.162
example error:
Err:15 http://ppa.launchpad.net/ondrej/php/ubuntu focal/main amd64 php7.4-dev amd64 7.4.22-1+ubuntu20.04.1+deb.sury.org+1
  Cannot initiate the connection to ppa.launchpad.net:80 (2001:67c:1560:8008::19). - connect (101: Network is unreachable) Could not connect to ppa.launchpad.net:80 (91.189.95.85), connection timed out [IP: 91.189.95.85 80]
Err:16 http://ppa.launchpad.net/ondrej/php/ubuntu focal/main amd64 php7.4-curl amd64 7.4.22-1+ubuntu20.04.1+deb.sury.org+1
example traceroute
+ traceroute ppa.launchpad.net
traceroute to ppa.launchpad.net (91.189.95.85), 30 hops max, 60 byte packets
 1 ip-10-203-198-141.ec2.internal (10.203.198.141) 0.159 ms 0.120 ms 0.092 ms
 2 ip-10-203-141-118.ec2.internal (10.203.141.118) 0.257 ms 0.269 ms 0.197 ms
 3 216.182.230.247 (216.182.230.247) 2.804 ms 216.182.226.162 (216.182.226.162) 9.377 ms 216.182.239.129 (216.182.239.129) 1.578 ms
 4 100.65.65.224 (100.65.65.224) 4.880 ms 100.65.56.240 (100.65.56.240) 7.470 ms *
 5 100.66.10.22 (100.66.10.22) 5.564 ms 100.66.14.194 (100.66.14.194) 18.036 ms 100.66.24.200 (100.66.24.200) 5.123 ms
 6 100.66.6.123 (100.66.6.123) 15.119 ms 100.66.7.245 (100.66.7.245) 5.440 ms 100.66.27.154 (100.66.27.154) 3.033 ms
 7 * 100.66.7.117 (100.66.7.117) 20.278 ms 100.66.5.53 (100.66.5.53) 18.122 ms
 8 100.66.5.163 (100.66.5.163) 5.871 ms 100.65.13.81 (100.65.13.81) 1.126 ms 100.66.5.119 (100.66.5.119) 22.425 ms
 9 52.93.29.47 (52.93.2

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1939927/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Tom Reynolds (tomreyn)]

Launchpad maintainers have asked those reporting similar issues on IRC to re-report them to https://answers.launchpad.net/launchpad/+addquestion (which they monitor). I am converting this bug report (which is clearly not a software bug but a network issue affecting the Launchpad.net instance of the Launchpad software) into such a question - so you can just continue reporting here.