Your most recent deployments all completed, and none of them show a failure that matches an error.

So we can tell what is going wrong, please share the exact error message (a screenshot works), where you see it (dashboard, CLI, build or deploy logs, or when visiting your app), which service it affects, and roughly when it happened in UTC.

The same 429 error!!!

The same 429 error!!

A 429 means "too many requests," and several different systems can send one, so the fix depends on where it comes from.

Please tell us where the 429 shows up: in the dashboard, in the CLI, from your own scripts calling our public API, on requests to your app's domain, or in your service's logs when it calls an outside service. Please also paste the full error text as you see it and roughly when it last happened, in UTC.

we are with the same Edge (railway-hikari) returning 429 "rate limited" and a heavy-traffic check on a low-traffic service

To trace a 429 "rate limited" response from our edge, we need two details: which service and domain are returning it, and the UTC times of a few of the failed requests. Please also include any x-railway-request-id values from those 429 responses, if they show one.