Replies: 3 comments 1 reply
-
|
Yes after GitHub started revamping it's ui, these problem started appearing i suggest you to use https://www.jsdelivr.com/github instead of GitHub cdn for these. |
Beta Was this translation helpful? Give feedback.
-
|
When visiting GitHub pages, the page load time is extremely slow. After analyzing the HAR file, I found the following: The bottleneck is github.githubassets.com (GitHub static assets CDN): Average request time: 57 seconds Breakdown: TTFB ≈ 25s, Download ≈ 32s This indicates that the assigned CDN node is very slow, with poor throughput. Other domains for comparison: github.com: average ≈ 16s, mostly HTML, acceptable. avatars.githubusercontent.com and fonts.gstatic.com: no significant issues. Conclusion: It’s not a local network or DNS issue, since tracert and ping are fine, and curl https://github.com/login completes in only 3 seconds. The issue only occurs when loading static assets from github.githubassets.com. Likely caused by suboptimal CDN node assignment or throttling. |
Beta Was this translation helpful? Give feedback.
-
|
The main GitHub homepage takes over 2 minutes to completely load when not yet cached by the browser: Here is the tracert if it helps: My public facing IP is 175.143.. from AS4788.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
General
Body
I hope I'm posting this to the right place. Much of the github.com website is inaccessible from my home network (I'm posting this from my work network). Using the developer tools in Chrome, I was able to determine that connections to github.githubassets.com were timing out. A tracert to that ends as:
6 18 ms 17 ms 17 ms 167.82.128.8
7 * * * Request timed out.
8 * * * Request timed out.
I looked up that last IP and it appears to be the Fastly CDN. I'm not sure where to go from here to troubleshoot further.

Beta Was this translation helpful? Give feedback.
All reactions