Summary: All services across both my projects show "Bad credentials" on the GitHub source connection. GitHub auto-deploy is broken project-wide. The error persists after a full revoke-and-reconnect cycle, so the per-repo link isn't the cause — the underlying GitHub authorization stored on my Railway account appears to be stuck/invalid and needs a server-side reset.

Railway account: a_vydrin@hotmail.com

GitHub account that owns the repos: alex-vydrin

Affected:

Project testfactory → service web → repo alex-vydrin/testfactory

Project signalflow → service signalflow → repo alex-vydrin/signal-flow

Both show "Bad credentials" under Settings → Source → Branch connected to production.

Symptom: Railway's backend gets a GitHub API 401 Bad credentials when reading the connected branch. Push-to-deploy no longer triggers builds.

What I've already tried (problem persists after every step):

Re-saved the Railway GitHub App installation on GitHub with All repositories access.

Disconnected the source repo on a service and reconnected it — "Bad credentials" returns immediately.

Revoked Railway's access on GitHub and reinstalled — no change.

What I've ruled out:

Not a Railway incident — status page shows 100% uptime on GitHub integration, deployments, and auth for the last 90 days.

Not my GitHub account — my own GitHub auth works fine; I can push and the gh CLI is authorized with repo/workflow scopes.

Not my local setup — correct remote (alex-vydrin/testfactory), production branch is master.

Railway CLI auth is healthy — railway whoami/status work and railway up deploys successfully, which is how I'm currently shipping as a workaround.

Likely cause / request: The GitHub identity binding on my Railway account (note the a_vydrin@hotmail.com Railway account vs alex-vydrin GitHub identity) seems to be in a stuck/invalid state that the normal disconnect-reconnect flow doesn't clear. Please reset/relink the GitHub integration on my account on your end so the source connection can re-authenticate.