13 days ago
For our service, can we disable HTTP logs containing client IP addresses, User-Agent strings, request IDs, and precise timestamps?
If not, can these fields be removed before the logs are stored?
What is the actual retention period for these logs, including any data that may become accessible again after upgrading our plan?
We are implementing privacy-preserving audience measurement and need to prevent these logs from being linked to individual users’ activity.
Application request logging, tracing, and automatic instrumentation are disabled. However, our deployment tests still appear in Railway’s HTTP logs with srcIp, clientUa, requestId, and precise timestamps.
Can these edge-generated logs be disabled or redacted for this service specifically? We are on the Hobby plan.
1 Replies
Status changed to Awaiting Railway Response Railway • 13 days ago
13 days ago
HTTP logs from our edge are recorded for every request to a public domain. There's no setting on any plan to turn them off for a service, and fields like client IP, User-Agent, request ID and timestamps can't be removed or redacted before they're stored. Log entries also can't be deleted or redacted after the fact, either one by one or in batches.
On retention, all logs, including HTTP logs, are stored for 90 days and then deleted automatically. Your plan's figure (7 days on Hobby, 30 on Pro) only controls how far back you can view them. That's why upgrading can make older logs visible again, as long as they're still inside the 90 days. Logs older than 90 days are gone, and we can't delete them sooner than that.
Status changed to Awaiting User Response sam-a • 13 days ago
6 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 6 days ago