Related: Which header should I rely on for real client IP?

I previously asked which header to rely on for the real client IP. At that time, X-Forwarded-For contained the correct IP. However, today the situation has changed — none of the headers contain my actual global IP anymore.

What I see

Tested with curl against a whoami container on whoami-production-233c.up.railway.app:

- X-Forwarded-For: 157.52.121.86 (single IP — no comma-separated list)

- X-Real-Ip: 157.52.121.86

My actual global IP is 126.144.31.92— it appears nowhere. (157.52.121.86 belongs to Fastly 157.52.64.0/18 )

I'd expect X-Forwarded-For to be 126.144.31.92, 157.52.121.86, but only the Fastly IP is present.

Questions

1. Is this an intentional change or a regression from recent infrastructure changes?
2. Is there any other way to obtain the real client IP?