New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
My budget doesn't allow for all of that yet; right now, I'm looking for a low-cost solution. Regarding blackholing, though—are there any providers that offer GEO/ASN filtering?
If so, I could block traffic from the US and EU, since my users are exclusively in the APAC region.
Currently, most attacks are originating from Brazil, Mexico, Russia, Ukraine, Argentina, and India.
are u okay with Germany in any case or sweden ?
If your audience is mainly from APAC region, why not make a geoip based firewall rules?
This is not a 100% solution but will save lots of wasted resources.
Because you still need enough bandwidth to receive all the packets so they can get to your firewall.
@Lostone: have you asked your provider what they can do for traffic blocking?
Sometimes that, too.
Yes, that's my plan, but it would be better to use a Geo Filter on the upstream side, wouldn't it?
Not yet; I'm currently looking.
Hi Lostone,
We offer Game/VPS services in Singapore with GCore DDOS Protection
https://wasabihosting.com
If you require specific games, we can take a look to have it supported.
try vibegames
no ipv6? owned or leased hardware?
XDP is excellent for dropping bad packets cheaply on the host, but it cannot help once a volumetric flood saturates the upstream link, so the filtering has to happen before that link. The practical middle path is a GRE tunnel from a game-aware scrubbing provider to a hidden origin: the public game IP lives at the scrubber, only clean traffic reaches your server, and the origin IP is never published in DNS or server lists. For the game layer itself, add protocol-aware checks where possible, such as validating the initial handshake and rate-limiting new sessions per source, because generic UDP rate limits tend to drop legitimate players during an attack. Start by measuring which attack type actually hurts you most, volumetric, protocol, or application-layer, since that decides whether you need more upstream capacity, better filtering, or both.
We can support IPv6 but GCore only protects IPv4 at the moment.
oh. cool thats neat. I never knew about you guys until yesterday