I also encountered the same issue after this update without making any code changes — the real IP of the requesting user was lost. I then added debug logging to the response and confirmed that the real client IP is completely absent from all request headers.

how can this have been ongoing for such a long time now

@Railway - any updates? Our customers are not able to access our services anymore...

Im having the same issue to, yesterday it started happening suddenly

any updates @Railway?

any updates @Railway?

Same issue at our organization, crucial infrastructure is failing bacause of this.

(Webhooks with ip checks, throttling on ip's etc)

This is the top issue for 24hours now. I don;t understand how they just ignore it. What's the purpose of this forum. To show how bad you manage things? Second dt of this time in a month.

This is really frustrating, why isn't anyone replying, our organization really depend on client Ips and it causing wide spread problems

Acknowledging this issue, we have raised it to our networking engineer.

Thank you!

Hey,

This has been fixed, no action is needed on your end.

We are sorry for introducing this regression and will be more diligent about changes to the behavior of headers going forward.