Skip to content
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

Broken CDN worker for repo.anaconda.com #1073

Closed
2 tasks done
kalebo opened this issue Dec 4, 2024 · 5 comments
Closed
2 tasks done

Broken CDN worker for repo.anaconda.com #1073

kalebo opened this issue Dec 4, 2024 · 5 comments
Assignees
Labels
severity::1 blocker; broken functionality with no workaround source::community catch-all for issues filed by community members type::bug describes erroneous operation, use severity::* to classify the type

Comments

@kalebo
Copy link

kalebo commented Dec 4, 2024

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

One of the cloudflare CDN workers for repo.anaconda.com seems to be broken for the Salt Lake City region. It returns 500 error codes for GET requests both within conda, as well via curl or a browser. It has been doing this for about 4 hours at this point.

Specifically, the error output is:

CondaHTTPError: HTTP 500 INTERNAL SERVER ERROR for url <https://repo.anaconda.com/pkgs/main/linux-64/repodata.json>
Elapsed: 00:06.508551
CF-RAY: 8ece52c17e992c69-SLC

Additional Context

No response

@kalebo kalebo added the type::bug describes erroneous operation, use severity::* to classify the type label Dec 4, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Dec 4, 2024
@chenghlee
Copy link
Contributor

Checked with Anaconda's infrastructure team: we identified a spike in HTTP 500 errors affecting ~1% of CDN traffic for repo.anaconda.com, starting around 2024-12-04 1600 UTC. The problem appears to be isolated to certain regions (so far: Detroit, Malaysia, and possibly Utah), and the issue seems to be on our CDN provider's side (CloudFlare). We've opened a ticket with them and will update the community as we get more information.

@jezdez jezdez added severity::1 blocker; broken functionality with no workaround source::community catch-all for issues filed by community members pending::support indicates user is waiting on support from triage engineers labels Dec 5, 2024
@jezdez jezdez moved this from 🆕 New to 🏗️ In Progress in 🧭 Planning Dec 5, 2024
@jezdez
Copy link
Member

jezdez commented Dec 5, 2024

We've opened an incident and published it on Anaconda's status page: https://anaconda.statuspage.io/incidents/qfv2n662hyym

@jezdez
Copy link
Member

jezdez commented Dec 5, 2024

It seems like the issue was found by the infrastructure provider and a fix is rolling out at the moment

@jezdez
Copy link
Member

jezdez commented Dec 5, 2024

Closing as completed following confirmation by Anaconda on https://anaconda.statuspage.io/incidents/qfv2n662hyym

@jezdez jezdez closed this as completed Dec 5, 2024
@github-project-automation github-project-automation bot moved this from 🏗️ In Progress to 🏁 Done in 🧭 Planning Dec 5, 2024
@jezdez jezdez removed the pending::support indicates user is waiting on support from triage engineers label Dec 5, 2024
@jakirkham
Copy link
Member

Thank you both! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity::1 blocker; broken functionality with no workaround source::community catch-all for issues filed by community members type::bug describes erroneous operation, use severity::* to classify the type
Projects
Archived in project
Development

No branches or pull requests

4 participants