Internal Redis pub/sub traffic within the same Railway project, when using the internal network (private networking), is not counted as charged Egress. Egress charges only apply to outbound traffic from your Railway services to external destinations on the internet. Communication between services—including Redis pub/sub—within the same project over the internal network is unmetered and not billed as Egress.

Hi. Thanks for the quick response. I don't have any other constant minute-by-minute data transfers to the external network. Could you provide the URL where such large volumes of data are being sent? I've thoroughly reviewed my code, and other than the pub sub channels on the internal network, I don't see any other outgoing data in the volumes I'm being charged for.

Hey, unfortunately Railway won't be able to provide that. I would recommend looking into Railway's HTTP Logs tab or using observability tools like Sentry or OpenTelemetry, as they're typically able to record any outgoing domains. Also, can you share a screenshot of your Egress metrics?

Are you sure you are using railways internal domains instead of public domains?

Yes, of course. Here's a screenshot showing egress at 25-30MB per minute (this is a 6-hour chart timeframe, and one dot equals approximately one minute).

Yes, that's right. Publishing is done via an internal join.

HTTP logs are empty

if you're running node you could try overwriting the global fetch and logging requests from there?