Sequin egress when not using public networking
newkind
PROOP

a month ago

Hi,

I'm using it for a sink between my Postgress -> Typesense. I have noticed that even though the Sequin database and Typesense connections are both configured to use the Railway private networking, there is still some egress happening on a public network (which obviously pays extra). I was just wondering if you have any idea what could cause this? I was using public domain but only to access the Sequin admin panel, all other services are using private networking, so I'm surprised by the numbers like 80 MB especially that this is a brand new deployment and the database is almost empty. For now I have just deleted the public networking address to stop this.

egress.jpg

Awaiting Template Creator Response

1 Replies

newkind
PROOP

a month ago

So looks like this was caused by the Sequin telemetry and crash reporting which would send up to 80 MB every couple minutes - it was almost 2 GB egress in less than 24h. For other folks dealing with that here's how to disable it: https://sequinstream.com/docs/reference/configuration#feature-configuration

tl;dr

SEQUIN_TELEMETRY_DISABLED=true

CRASH_REPORTING_DISABLED=true

The red line shows when I disabled telemetry on mine:

CleanShot 2026-07-09 at 13.24.44.jpg

Attachments


Welcome!

Sign in to your Railway account to join the conversation.

Loading...