Ask HN: GitHub OAuth Flows Failures?
Several users are experiencing failures in GitHub OAuth browser flows since this morning. While tokens can be obtained, subsequent GitHub API calls are returning non-200 or empty responses, affecting company workflows.
Background
- GitHub OAuth flow: A standard way for third-party apps (e.g., your company's internal tool) to let users log in using their GitHub account. The app gets a token from GitHub, then uses that token to call GitHub's API (e.g., to fetch user data or check permissions).
- "Non-200 or empty responses": HTTP status codes like 200 mean success. Non-200 codes (e.g., 401, 403, 500) or empty replies indicate the API call failed, even though the token was issued successfully.
- This matters because many companies rely on GitHub OAuth for authentication and CI/CD pipelines; a silent partial failure (token works, API doesn't) is harder to debug than a total outage.
- As of this Ask HN post (March 2025), no official GitHub status page announcement had been made, leaving developers to compare notes and suspect an unannounced server-side change or degradation.