Egress and Ingress
mendesdevel0per
PROOP

a month ago

Hello!

I’ve noticed that my frontend is receiving an abnormal volume of requests—apparently stemming from an attack or scraping activity—which is causing a significant spike in Public Network Traffic usage and, consequently, platform costs.

I would like to know if Railway has any mitigation mechanisms for this type of situation, such as protection against malicious traffic, rate limiting, infrastructure-level blocking, or any other recommendations to reduce this usage.

If there are any configurations I can apply or specific best practices for this scenario, I would greatly appreciate your guidance.

Thanks for your time!

Solved$20 Bounty

Pinned Solution

a month ago

The most easy approach would be to put Cloudflare in front of your application, it has rate limit at edge, block by IP reputation, user agent... Free plan is enough for this.

I would also add some rate limiting rules to see if it solves your issue.

6 Replies

mendesdevel0per
PROOP

a month ago

image.png

Attachments


Railway
BOT

a month ago

You can enable Under Attack Mode on your service's Settings page under the "Edge" section, which presents a browser check to visitors and blocks bot/script traffic before it reaches your service. It can be set to auto-expire after 1, 3, 12, or 24 hours, or left on until you deactivate it.


Status changed to Awaiting User Response Railway about 1 month ago


mendesdevel0per
PROOP

a month ago

And what else can I do to prevent it? Because I can't always keep that enabled.


Status changed to Awaiting Railway Response Railway about 1 month ago


Railway
BOT

a month ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway about 1 month ago


a month ago

The most easy approach would be to put Cloudflare in front of your application, it has rate limit at edge, block by IP reputation, user agent... Free plan is enough for this.

I would also add some rate limiting rules to see if it solves your issue.


medim

The most easy approach would be to put Cloudflare in front of your application, it has rate limit at edge, block by IP reputation, user agent... Free plan is enough for this. I would also add some rate limiting rules to see if it solves your issue.

mendesdevel0per
PROOP

a month ago

Eu utilizo, mas mesmo assim algo acontece, talvez tenha que assinar o plano Pro, obrigado!


a month ago

Try tweaking some settings, blocking bots, checking rate limit rules, enable WAF....

I don't think upgrading to Pro will immediately fix your issue.


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved mendesdevel0per about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...