Public GitHub profile returns 404 for everyone except me

[feq4n]

My GitHub account is accessible when I'm signed in, but my public profile returns 404 for everyone else. The username is feq4n. I can create repositories and use my account normally, but https://github.com/feq4n and the GitHub API return 404 when accessed publicly. Could you check if my account has been flagged or if there is a visibility issue?

[jrb00013]

yo i just checked from outside your login:

• https://github.com/feq4n → 200 OK for me
• API users/feq4n returns your profile fine (public, 21 repos, name Feqan Gerayli)

so right now your public profile is not 404ing. either github fixed whatever flag/glitch it was, or whatever was caching the 404 on your friends' side went stale.

quick things for anyone still seeing 404:

1. hard refresh / different browser / phone data (not wifi)
2. make sure they're hitting https://github.com/feq4n exactly (typo / old username)
3. if you still see yourself fine but strangers 404, have them try the API: https://api.github.com/users/feq4n — if that works, it's a frontend/cache weirdness on their end

if it starts 404ing publicly again for everyone including logged-out you, then yeah that's account/flag territory → open a support ticket. but as of this comment, the account looks publicly visible.

[frostyfoxie]

Hi I am also facing exact same issues can you please tell if your account issues are resolved? If yes then how?

My profile had 30 repositories, 2k+ commits its 3+ years old it is showing error 404 since yesterday on all the URLs when opened without logging into the account. https://github.com/frostyfoxie

Earlier the GitHub api fetching called account to be spammy, but now reads error 404 even though I'm able to access it when logged in.

[PrithwishDas101]

A 404 here doesn't necessarily mean the profile was deleted. The important distinction is whether the account is actually returning 404 from GitHub's public API as well.

I'd test from a completely unauthenticated environment:

curl -i https://github.com/frostyfoxie
curl -i https://api.github.com/users/frostyfoxie

Also compare authenticated vs unauthenticated requests. If the profile is visible while logged in but both unauthenticated endpoints consistently return "404", that's unlikely to be a browser cache issue.

In particular, GitHub intentionally uses "404" for some account/resource states rather than exposing whether an account exists. If the API previously returned something like "spam"/suspension-related information and has now changed to "404", that would be a stronger indication that the account is being filtered at the platform level rather than the profile simply having a visibility setting changed.

I'd also check whether individual public repository URLs return 404 while logged out:

curl -I https://github.com/frostyfoxie/

If the account owner can access the repositories while authenticated but anonymous requests consistently return 404 for the profile, repositories, and API, there isn't really a client-side fix to apply. Clearing cache, changing browsers, or changing profile visibility won't resolve an account-level restriction.

At that point the correct escalation path is GitHub Support. Include:

• username
• approximate time the public 404 started
• authenticated vs unauthenticated results
• "curl -i" response headers/status
• whether "api.github.com/users/" returns 404
• whether public repositories are also inaccessible anonymously

I would avoid repeatedly changing repositories/profile settings until Support confirms the account state, since the evidence points more toward an account/platform-side restriction than a normal profile configuration problem.

[adi785]

I’ve seen a similar issue before where the account worked normally while signed in, but the public profile returned a 404 when accessed anonymously.

One thing I’d recommend checking is whether the account’s public repositories are still accessible. If repositories under feq4n are publicly visible while https://github.com/feq4n returns 404, that would suggest this is more likely a profile visibility/indexing or GitHub-side issue rather than the account being completely suspended or deleted.

I’d also try:

• Opening the profile in an incognito/private window
• Checking from a different network/device
• Testing the public API: https://api.github.com/users/feq4n
• Checking whether https://github.com/feq4n/<public-repository> still works

If all of those consistently return 404 for anonymous users while the account works normally when signed in, I’d recommend contacting GitHub Support and linking to the affected profile and a few public repositories. They should be able to check whether there is an account-level visibility or moderation restriction that isn't exposed publicly.

I wouldn’t assume the account has been flagged solely based on the 404, since GitHub can also return 404 for several visibility-related reasons.