Launchpad itself

IP addresses being blocked / throttled by ppa.launchpad.net

Asked by Doug Wehmeier

We believe that some of our IP addresses may be being blocked or throttled when trying to fetch packages from ppa.launchpad.net.

In the last couple of days we have started seeing failures from build containers that have not been changed. apt-get fails after timing out on fetches to ppa.launchpad.net. When we attempt to build the same containers on other networks, they work correctly.

Packages from archive.ubuntu.com and other sources fetch successfully, and we have not found any issues in our routing, DNS, etc.

If someone can reach out, I can share the affected IP address ranges, but would prefer not to post them publicly.

Thanks

Question information

Language:
English Edit question
Status:
Expired
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Tom Wardill (twom) said : 		#1

Hi,

Is this from AWS?
We've seen multiple reports over the last couple of days of people experiencing problems accessing ppa.launchpad.net from inside AWS. It's currently being investigated, but I'm afraid we have no timescale for a fix at the minute.

Revision history for this message
Doug Wehmeier (quailman) said : 		#2

Hey Tom, yep that's correct the affected IPs are through AWS.

It's possible AWS is doing something to outgoing requests, but from what
I'm seeing the problem appears to be narrowly limited to ppa.launchpad.net
connections which 99% of the time is because someone blocked an ip range on
the receiving server (probably for a good reason).

I also appear to be able to make individual curl calls successfully, but
when apt-get tries to fetch multiple packages quickly the requests time
out. This looks like throttling to me, as opposed to a bad routing table or
something like that.

Let me know if I can help diagnose. This is a major blocker for us.

On Fri, Aug 13, 2021, 4:55 AM Tom Wardill <
<email address hidden>> wrote:

> Your question #698356 on Launchpad itself changed:
> https://answers.launchpad.net/launchpad/+question/698356
>
> Status: Open => Needs information
>
> Tom Wardill requested more information:
> Hi,
>
> Is this from AWS?
> We've seen multiple reports over the last couple of days of people
> experiencing problems accessing ppa.launchpad.net from inside AWS. It's
> currently being investigated, but I'm afraid we have no timescale for a fix
> at the minute.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/launchpad/+question/698356
>
> You received this question notification because you asked the question.
>

Revision history for this message
Ralph Schindler (ralphschindler) said : 		#3

I too am having this issue from a residential cox connection geographically from New Orleans, La. I have been seeing this problem for the last week.

These are the 2 support posts I've put out there:

https://forums.cox.com/forum_home/internet_forum/f/internet-forum/29260/connection-blocking-to-specific-ip-address

https://www.dslreports.com/forum/r33185289-Connection-blocking-limiting-to-specific-IP-address

This is a major blocker for me too. Thanks.

Revision history for this message
Colin Watson (cjwatson) said (last edit ): 		#4

@ralphschindler This may be a separate issue, and at any rate we should treat it separately as there's currently no evidence that it's related to the AWS/HE routing issue. Could you please file a ticket with our sysadmins by sending email to <email address hidden>, and include as much detail as you can, including the output of "mtr --report -T -P 80 ppa.launchpad.net"?

I'm setting this question's status back to "Open", as "Needs Information" means that we need information from you, not that you need information from us.

Revision history for this message
Ralph Schindler (ralphschindler) said : 		#5

Sorry about that, was not sure which button to click. I will send in a separate report, thank you!

Revision history for this message
Launchpad Janitor (janitor) said : 		#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.