No visibility in egress costs
devcsrj
PROOP

2 years ago

On one of my services (027b6ff3-a5b1-4c74-a272-46b5966ad7fa), the egress cost suddenly spiked 132.34 GB (costing $13.2336). While I have an idea on why:

  • Use of DATABASE_URL instead of DATABASE_PRIVATE_URL
  • Uploading of images to S3

It is unclear whether this is enough to control the costs, or how much each bullet affected the egress cost.

Can Railway provide a breakdown? Anything that gives insight on what exactly is the traffic going out of the service that caused this spike

0 Replies

Welcome!

Sign in to your Railway account to join the conversation.

Loading...