The srcIp field in HTTP logs reflects the IP address that directly connected to our edge network. If your traffic is routed through Fastly (or any CDN/proxy), our edge sees Fastly as the connecting client, so its IP appears in srcIp. To get the real client IP, your application can read the X-Forwarded-For header from the incoming request.

I'm seeing exactly the same behavior on my side.

A few hours ago, I was consistently getting my real client IP in X-Forwarded-For (e.g. 190.xxx.xxx.xxx), but now it only shows Fastly IPs (140.248.x.x / 157.52.x.x), and the real IP is completely missing from all headers.

So in my case, reading X-Forwarded-For doesn't solve it anymore — it just returns the edge IP.

This started around the same time as the recent Fastly/Railway incident, so it might be related.

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

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.