GitHub Pages 404s & Account Desync: A Critical Blip in Software Project Visibility

In the fast-paced world of software development, maintaining consistent visibility into project status is paramount. When core services falter, it can create significant headaches for developers and impact how software project metrics are perceived. A recent GitHub Community discussion highlighted a particularly perplexing issue where multiple GitHub Pages sites, along with public API endpoints, mysteriously returned 404 errors despite all systems reporting successful builds.

The Case of the Disappearing Pages

The discussion, initiated by user rustyisacat, detailed a widespread outage affecting seven GitHub Pages sites under both a personal account and an organization (rusty-workshop). Around September 3, 2026, all custom domains and even the default *.github.io URLs for these projects began returning "404 Site not found."

• Widespread Impact: Seven sites across two accounts, suggesting a broader platform issue rather than individual misconfiguration.
• Conflicting Status: GitHub's own API reported "status":"built" for all affected repositories, with no errors in the build logs. Yet, the sites were inaccessible.
• Custom Domain Block: On the main user site, the previously verified custom domain was unexpectedly null, and attempts to re-add it via API or UI failed with the message: "You cannot set a custom domain at this time."
• Limited Recovery: While some organization repos allowed disabling and re-enabling Pages and re-setting custom domains, the 404s persisted.

What Was Ruled Out?

The user meticulously ruled out common culprits:

• DNS Issues: Verified that all domains correctly resolved as CNAMEs.
• General Outage: Other unrelated GitHub Pages sites loaded fine, and GitHub's public status page showed no incidents.
• Build Failures: All recent builds reported success.

Beyond Pages: An Account-Level Desync

The situation escalated when rustyisacat discovered the issue wasn't confined to GitHub Pages. The public API for their own account was also returning a 404, indicating a deeper problem:

$ curl -s https://api.github.com/users/rustyisacat
{"message":"Not Found","documentation_url":"https://docs.github.com/rest","status":"404"}

Crucially, the authenticated view of the account (GET /user) worked perfectly, returning all correct data. This pointed to a significant "account-level desync" – where the public-facing representation of the user's account and its associated repositories was out of sync with the underlying, authenticated data.

This finding was critical; even creating a new throwaway repository failed because the gh repo create command relies on the public users/rustyisacat endpoint to resolve the owner, which was returning a 404.

Implications for Project Visibility and Metrics

Such an outage, even if localized to specific accounts, underscores the fragility of relying solely on public-facing data for accurate software project metrics. When public repositories and their associated Pages sites become inaccessible, it directly impacts how engineering managers assess and report on project status. Imagine trying to showcase a live demo, share a project's documentation, or even pull data for a git metrics dashboard when core public endpoints are failing. This scenario highlights the critical importance of robust platform stability and clear communication channels when such desyncs occur.

While the discussion doesn't provide a resolution, it serves as a powerful reminder for developers and organizations to consider redundancy and monitoring strategies for their public-facing assets, especially when these assets contribute to critical kpi for engineering manager reporting and overall project transparency.