What's going on with GitHub?

[Rod-at-DOH]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Other

Body

I'm trying to open a repo in one of our GitHub Organizations. I've gone to the home page for the repo and have been waiting for it to finish rendering the page.

... and waiting...

... and waiting...

After about 20 minutes all I'm seeing is:

and this on the right side of the page:

I expected something to be rendered after 20 minutes, but nothing has happened. I've circled in red where details should appear, but nothing has happened after 20 minutes. I closed my browser and reopened it, but that didn't work.

This is the behavior for MS Edge. When I try going to the page in Chrome, all it gives me is a blank page.

So, what's going on?

[danilablagorodniy37]

Hey! GitHub isn’t down right now. The status page shows everything working, so it’s probably something on your side.

The blank page in Chrome and the grey boxes in Edge usually mean the page’s scripts aren’t loading. A few quick things to try:

Open the repo in a private/incognito window. If it works there, an extension (like an ad blocker) is the problem.
Try it on your phone using mobile data. If it works there, your work network or firewall is probably blocking GitHub’s files (like githubassets.com). Your IT team can check that.
Try another repo in the same org. If only this one is broken, contact GitHub Support with the repo link.

[Rod-at-DOH]

Hi @danilablagorodniy37,

I tried private mode, it didn't help.

I have 3 extensions, one of which is put in place by my IT department, and I can do nothing about that. But I did disable the LastPass extension. (It surprises me that it was enabled, because my CISO forbids it so I thought it was gone.) That seems to have done the trick. So, I thought I'd mention that here, in hopes that this might help others.

[tanisha-gu]

Things to try, roughly in order:

Hard refresh (Ctrl+Shift+R / Cmd+Shift+R), then try an incognito/private window with extensions disabled. Ad blockers, privacy extensions, and corporate security extensions often block GitHub’s async calls.
Check githubstatus.com for degraded “API Requests”, “Webhooks”, or “Issues/Pull Requests” incidents.
Rule out your network. A corporate proxy, firewall, or VPN may be blocking some GitHub endpoints (e.g. api.github.com, github.githubassets.com, *.githubusercontent.com). Try a different network, such as a phone hotspot.
Check the Network tab. Open dev tools (F12) → Network, reload, and look for requests that are red, stuck on “pending”, or returning 4xx/5xx. The failing URLs will show whether this is a block on your side or a server-side problem.
See if it’s specific to this org or repo. Try another repo in the same org and a public repo elsewhere. If only this org’s repos fail, check for SAML SSO: if your org enforces it and your session isn’t authorized, some requests can fail in odd ways. Visit the org page and re-authorize.
Confirm the repo itself is fine. If git clone works from the command line, the repo data is healthy and the problem is only in web UI rendering.