All github.com/…/raw/… URLs return HTTP 504 globally since ~09:00 UTC (raw.githubusercontent.com unaffected)

[Tauris]

🏷️ Discussion Type

Bug

Body

Since at least 08:59 UTC today (8 Nov 2026), every raw-file URL of the form https://github.com///raw// returns HTTP 504 after about 11 seconds, for any repository. /blob//?raw=true fails the same way.

Reproduce with any repo, e.g.
curl -sI https://github.com/microsoft/vscode/raw/main/README.md → HTTP/1.1 504 after ~11 s

The redirect target is fine throughout:
curl -sI https://raw.githubusercontent.com/microsoft/vscode/main/README.md → HTTP/1.1 200 in ~0.2 s

Not regional: 10 Globalping probes (US ×2, GB, DE, FR, NL, JP, SG, AU, BR) at 09:52 UTC all got 504 after 11.0–11.7 s. Still failing at 10:04 UTC. githubstatus.com shows no incident.

Impact: anything that uses the github.com raw route — userscript @updateURL/@downloadurl, curl in install scripts, raw links in docs. Affected in my case: https://github.com/Tauris/threadcalm/raw/main/dist/threadcalm.user.js (works as https://raw.githubusercontent.com/Tauris/threadcalm/main/dist/threadcalm.user.js).

Is anyone else seeing this? Workaround until it's fixed: use the raw.githubusercontent.com form directly.

githubstatus.com has shown no incident for the whole hour; a support ticket about this was auto-closed as "self-service", so this thread is the only report I can file.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[RuslanSemchenko]

Same problem

[foonerd]

This is infrastructure back-end problem, in my case, workflows have not changed for weeks. Right now, entire build train fails on the same type of curl requests with 504 as reported before. The DownDetector is in red, whilst GitHub status page shows everything in order.

I doubt any GitHub techs are reading these comments.