GitHub web UI fails to hydrate (ChunkLoadError, dead header)

[likikambidi]

Select Topic Area

Product Feedback

Body

Hi GitHub Support,

I’m seeing a persistent frontend failure on github.com in Chrome where the UI shell renders but does not hydrate.

Symptoms:

Header navigation (search, hamburger, profile) is non-responsive
Repo pages sometimes show “Looks like something went wrong!”
DevTools consistently reports ChunkLoadError: Loading chunk failed after 3 retries

Troubleshooting already done:

Cleared cache/cookies/IndexedDB, unregistered service workers
Disabled all extensions, reset Chrome flags, tested Incognito
Issue persists; works in other browsers / fresh profiles
This looks like a CDN / chunk delivery or hydration issue specific to this Chrome environment.

Thanks for any guidance or confirmation if this is a known rollout issue.

[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. ⭐

[MohamedAminGrami]

Issues like this are typically related to:

• CDN cache inconsistencies serving outdated or mismatched chunks
• A failed or partial frontend rollout
• Edge cases in Chrome’s cache or compression handling that affect chunk loading

At this point, the most likely resolution would be on the platform side (cache invalidation or rollout stabilization). If possible, it may help to monitor whether the issue resolves after a frontend deployment or cache refresh. In the meantime, using an alternative browser is a reasonable workaround.

Hopefully this can be confirmed or investigated further as a known issue on your end.