Thanks for the report. We can't speak definitively as we're investigating, but there were a small number of similar reports which are possibly related.

To aid our investigation, would it be possible to provide more details e.g. the time window of intermittency and the % of services affected. That would be a huge help, many thanks.

5:11 PM, it was just the one service, the production deployment, was resolved after we did a redeploy.

Thanks for the added info. Just to let you know, our investigation will continue into next week as there is a specific network engineer we'd like to dig into this.

Hi,

Continuing on the same thread, as we have a similar issue with edgeRegion:"europe-west4".

Many API requests to our server are diverted to this proxy.

Most of these are resulting in 404 errors.

Is it possible to not send traffic to this region for a while?

Timeline of Requests: 2PM IST to 10PM IST.

One Service Only.

Hi,

Continuing on the same thread, as we have a similar issue with edgeRegion:"europe-west4".

Many API requests to our server are diverted to this proxy.

Most of these are resulting in 404 errors.

Is it possible to not send traffic to this region for a while?

Timeline of Requests: 2PM IST to 10PM IST.

One Service Only.

Hey, could you create your own thread please?

A 404 error is typically not from us. We only send a 404 when there's no application hosted at the Railway domain. If you can see that within your HTTP Logs, it means your application is the one returning the 404 response that we forward along our proxy.