[2026-02-27] Incident Thread

[github-actions[bot]]

❗ An incident has been declared:

Code view fails to load when content contains some non-ASCII characters

Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.

[github-actions[bot]]

Update

We are looking into recent code changes to mitigate the error loading some code view pages.

[pratikrath126]

Thanks for opening this thread to track the incident. Regarding the non-ASCII character issue in the Code view, does this affect only specific file types (like .md or .json) or is it a general rendering issue across all files? Appreciate the team keeping us updated on the progress!

[CSharperMantle]

There are other threads reporting the same (one from myself): https://github.com/orgs/community/discussions/188151, https://github.com/orgs/community/discussions/188152. It seems to affect directory listing and Wiki.

[github-actions[bot]]

Update

We have performed a mitigation but some repositories may still see issues. We are working on a full mitigation.

[github-actions[bot]]

Update

We have mitigated the issue but are working on invalidating caches in order to fix the issue for all impacted repos.

[github-actions[bot]]

Update

We have cleared all caches and everything is operating normally.

[github-actions[bot]]

Incident Resolved

This incident has been resolved.

[idm-ryou]

Just to report, our Wiki is still affected by this issue and hasn't recovered yet.
https://github.com/orgs/community/discussions/188151

[chibicco]

FYI — even after today’s bug fix, the wiki links were still broken for us. Pushing an empty commit to the wiki repo fixed the links.

[77web]

Our wikis are back finally(without workaround, just waited for a day).

[github-actions[bot]]

Incident Summary

Starting February 26, 2026 at 22:10 UTC through February 27, 05:50 UTC, the repository browsing UI was degraded and users were unable to load pages for files and directories with non-ASCII characters (including Japanese, Chinese, and other non-Latin scripts). On average, the error rate was 0.014% and peaked at 0.06% of requests to the service. Affected users saw 404 errors when navigating to repository directories and files with non-ASCII names. This was due to a code change that altered how file and directory names were processed, which caused incorrectly formatted data to be stored in an application cache.

We mitigated the incident by deploying a fix that invalidated the affected cache entries and progressively rolling it out across all production environments.

We are working to improve our pre-production testing to cover non-ASCII character handling, establish better cache invalidation mechanisms, and enhance our monitoring to detect this type of failure mode earlier, to reduce our time to detection and mitigation of issues like this one in the future.

[MHassan-Tariq]

This is a critical update for anyone working within the GitHub ecosystem. An incident regarding Code View failures due to non-ASCII characters can disrupt code reviews, PR approvals, and general repository navigation.

Since you are currently in the middle of a 30-day LinkedIn challenge and building LPG Nexus, this incident might actually be a great "real-time" technical topic for you to share with your network. It demonstrates that you are plugged into the industry's pulse.

Quick Actions You Should Take
Avoid +1 Comments: As requested in the incident report, do not comment "+1" or "Me too." Use the Subscribe button on the GitHub Discussion page and use Emoji reactions to stay updated without cluttering the thread.

Check Your Files: If you are working on your E-learning platform or LPG Nexus and notice your code isn't loading, check for special characters (emojis in strings, accented characters, or non-standard symbols) that might be triggering the bug.

Local Development: While the web view might be down, your local git operations (pull, push, commit) should remain unaffected. Rely on your local editor (VS Code/Cursor) for code reviews until the fix is deployed.

Turn This Into Content (LinkedIn Post Idea)
You can use this incident to show your followers how a Full Stack Engineer handles platform-wide bugs.

Draft Post:

"Ever had your GitHub Code View just... disappear? 📉

Currently, there’s an active incident on GitHub where Code View fails to load if your files contain non-ASCII characters. It’s a great reminder of how sensitive encoding can be in large-scale systems.

While the GitHub team works on a fix, I’m shifting my code reviews to my local environment. If you're seeing a 'fail to load' screen on your PRs today, check for emojis or special characters in your strings!

Staying agile and moving the work to local while the cloud catches up. 💻🔥

#GitHub #WebDev #FullStackEngineer #LPGNexus #CodingIncident"