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

Resolved

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.

Investigating

We have cleared all caches and everything is operating normally.

Investigating

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

Investigating

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

Investigating

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

Investigating

We are investigating reports of impacted performance for some GitHub services.