Your haystack service's last successful deployment was on 2026-05-14 at 18:09 UTC, so the service itself is running fine. The 404 errors you're seeing are from a manually added webhook in GitHub, which won't work because auto-deploy is handled entirely through the Railway GitHub App, not manual webhooks. Please remove any manually created webhooks, then verify the Railway GitHub App has access to this repository at github.com/settings/installations, accept any pending permission updates, and try disconnecting and reconnecting the repo in your service settings. If commits still don't trigger deploys after that, uninstalling and reinstalling the Railway GitHub App should resolve it.

I was advised by my railway agent to create the manual webhook because the railway app based one was also erroring out

We understand the Railway GitHub App webhook itself was also failing, not just the manual one. To deploy in the meantime, you can open the Command Palette (CMD+K) and select "Deploy Latest Commit." To investigate the webhook delivery issue further, could you share the GitHub repository name, the connected branch, and the commit SHA(s) that did not trigger a deploy?

I did the command palette deploy and that also threw an error.

Repo: https://github.com/isArrayDesigner/haystack

Branch: Main

commit SHA: https://github.com/isArrayDesigner/haystack/commit/d6042c1820a9034baa223403492f0c90231af8f0

Same issue, I just sent an email to support: This is a Railway platform issue. The webhook isn't firing despite being authorized and enabled. and the manual deploy is also failing with an HTTP error.

Originally, it is showing me as a coming from an invalid region despite bing on US East VA. Something wonky today

Definitely - I don't usually have issues. Even the agent has confirmed that it's a railway error.

Mine finally got fixed, not sure when but the deploy option finally showed up and was able to with zero errors on the build. Hope you got yours sorted!

Same - there was definitely something going on, but surprisingly it isn't showing as a blip on their status page.

Glad it resolved for both of you. This looks like a transient GitHub token authentication error during that window, which would have prevented both webhook-triggered and manual deploys. The issue cleared up on its own. Apologies for the disruption.