We experienced a major service disruption today from 02:25 UTC to 07:57 UTC that affected GitHub integrations, build machines, and the dashboard, which directly explains the 500 errors from railway up, GitHub pushes not triggering deployments, and "Deploy Latest Commit" not responding. Your existing deployment from May 18 is still running and serving traffic normally. The incident is now resolved, so pushing a new commit or clicking "Deploy Latest Commit" should work again. If deployments still aren't triggering, please try disconnecting and reconnecting the GitHub repo in your service settings.

Seems like Railway up is working now, but GitHub pushes are still not visible.

GitHub webhooks sent during the outage were likely lost and won't be retried by GitHub, which is why those pushes aren't visible. We see a new deployment was triggered on your service at 09:26 UTC and is currently initializing. For future pushes, try disconnecting and reconnecting the GitHub repo in your service settings to re-establish the webhook connection, and if that doesn't work, check your GitHub installation settings at https://github.com/settings/installations to ensure the Railway app has the correct permissions.