-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub Releases: Status 503 Egress is over the account limit. #121
Comments
This message is from (the Microsoft-owned) Azure and says (the Microsoft-owned) GitHub has reached the egress limit on their blob storage account. The Azure docs mention an egress limit of 120Gbps, which I guess might apply to the whole of GitHub Releases. https://docs.microsoft.com/en-us/azure/storage/common/scalability-targets-standard-account @MylesBorins Is this a known limitation of GitHub Releases? |
The only other example I can find of this specific error message in relation to GitHub Releases is from 3 days ago, which suggests this might be a new problem. |
@lovell would you be able to open a ticket with GitHub support so we can track this internally. I'll escalate to the appropriate folks |
@MylesBorins Thank you for the quick response, support ticket 1419586 created for this. |
I got a reply from GitHub support, which quotes the same URL I provided:
This appears to confirm that GitHub Releases:
Many others are reporting the same problem at community/community#8535 Anyone else experiencing this should contact GitHub support to provide more evidence via https://support.github.com |
I wonder if it would make sense to load the binary via e.g. Cloudflare instead of direct from GitHub |
Follow up response from GitHub support:
|
Got the same while downloading kubectl
|
Further response from GitHub support:
|
It looks like release assets are being served via S3 again, specifically the us-east-1 region, so my best guess would be that this was a cascading failure situation related to yesterday's AWS outage. |
Thank you for keeping this thread updated on what was going on with GitHub, Azure, and AWS, despite it being well beyond the scope of this project. Best wishes and happy holidays. |
It doesn't seem fully resolved, we just hit the error in our CI right now. 😅
|
If you are experiencing this problem, please contact GitHub support via https://support.github.com |
Hello! I tried installing sharp for a new project this morning and ran into an issue with this repository.
What I did:
What I got:
I reran the install command with the AWS Lambda instructions, which then worked, though it looks like that command also downloaded resources from this repository. For future reference, should I just keep retrying the install command until GitHub sends the binaries?
The text was updated successfully, but these errors were encountered: