We experienced a major platform-wide service disruption from 02:25 UTC to 07:57 UTC on May 20 that affected builds, deployments, and GitHub integrations. Your service's latest deployment succeeded at 09:00 UTC after the incident was resolved, and it appears to be running normally now. If pushes to your main branch are still not triggering deployments, try disconnecting and reconnecting the GitHub repo in your service settings.

Auto deploy still not working after reconnecting GitHub.I see "Auto deploys when pushed to GitHub" in settings but pushes don't trigger deployments.

Project ID: 73a63759-1747-4739-8da1-51bf2c248c47

Service ID: ce3d0020-96e4-4888-9478-f13076941901

Please fix the webhook manually on your side.

Since reconnecting the repo didn't help, please try these steps in your GitHub installation settings: confirm the Railway GitHub App has access to your repository and that there are no pending permission updates. Then back in your project canvas, click Add > GitHub Repository > Refresh to force a cache refresh. If that still doesn't work, uninstall the Railway GitHub App from GitHub entirely and reinstall it - this resets the webhook configuration. You can also check your deployment history for any skipped deployments (click "Show Skipped" in the deployments tab) and verify no watch paths are filtering out your commits.

Note that we are still working through a large backlog of deployments which means it make take some time to redeploy. (At the moment, Hobby deployments are paused while we try to catch up.) https://status.railway.com/incident/KVZ1Z8GY