Does billed Network Egress include TCP ACK traffic?
mmyr10392-sys
HOBBYOP

a month ago

Hi Railway team,

I found the existing thread “High Egress issues with WebSocket connections (TCP ACK overhead)”, but I could not find an authoritative answer from Railway about the actual billing/accounting behavior.

I need clarification on one specific point:

Does Railway's billed Network Egress / NETWORK_TX_GB include TCP ACK packets generated by the operating system in response to inbound TCP/WebSocket traffic?

My service receives approximately 400–450 MB/min of inbound WebSocket traffic while Railway reports approximately 25–26 MB/min of outbound traffic, giving an RX:TX ratio around 16–18:1.

The application itself does not appear to generate enough outbound payload to explain the measured TX.

For example, if a Railway service receives 500 GB of WebSocket/TCP traffic but sends very little application payload, are TCP ACK packets and TCP/IP/TLS protocol overhead generated in response to that inbound traffic included in NETWORK_TX_GB and charged as Network Egress?

I am specifically asking about Railway's network accounting/billing layer, rather than general TCP behavior.

Thanks!

Solved$10 Bounty

2 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 1 month ago


a month ago

Hey! Yes, Railway's billed network egress is all outbound data leaving the private network and that includes TCP/IP headers and ACKs. I remember having this exact question a long time ago, and my issue was something else because ACKs are like 40-50 bytes so it only matters at very high pps


medim

Hey! Yes, Railway's billed network egress is all outbound data leaving the private network and that includes TCP/IP headers and ACKs. I remember having this exact question a long time ago, and my issue was something else because ACKs are like 40-50 bytes so it only matters at very high pps

mmyr10392-sys
HOBBYOP

a month ago

Thanks, this is very helpful.

Just to make sure before I base an architectural/cost decision on this: is the inclusion of TCP ACKs and TCP/IP overhead in billed Network Egress / NETWORK_TX_GB confirmed Railway accounting behavior?

If someone from the Railway team could confirm this specific point, that would be greatly appreciated.


Status changed to Solved medim • 8 minutes ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...