High egress without justification
knajjars
HOBBYOP

a year ago

Hi Railway team,

I was checking the status of my app today and it is down due to it reaching the spend limit I had setup. I was investigating in the logs and everything seems normal, but my egress went from ~80mb to 150gb from one day to the other. There is nothing in the logs, the usage I have for my API deployed to Railway should never reach this limit, even my DB provider bandwidth is normal (350mb). Not sure want happened here?

6 Replies

knajjars
HOBBYOP

a year ago

This is my DB provider bandwidth, the only data that my API has access to, You can see that for the entire billing period of august it is 350mb

Attachments


brody
EMPLOYEE

a year ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody over 1 year ago


knajjars
HOBBYOP

a year ago

can anybody from Railway help me investigate this? my service is down


brody
EMPLOYEE

a year ago

The traffic readout is correct.

We do not have any kind of tracing for web traffic so we have no way of telling you where your traffic went to, but you are connecting to redis over the public network, so your egress could come from that.


knajjars
HOBBYOP

a year ago

hey @brody thanks for the reply. As far as i can tell I setup the connection to Redis in the private network. Am I missing something?

Attachments


knajjars
HOBBYOP

a year ago

Also the numbers don't really match with usage, the service had a 120gb spike in egress within a few seconds and no logs from Railway or my service can show any abnormal activity at all, this also includes logs from Cloudflare, my DB provider and my deployed API instance.. To be honest this is all very strange to me, also checked Redis usage and nothing out of the ordinary.


brody
EMPLOYEE

a year ago

I see you have since updated the Redis environment variable on your service to the private networking URL.

You'll just need to fix the errors in your build logs and you should be good to go!


Loading...