Remote DDoS Protection
Team-assisted setupProtected IPv4 forwarding for an existing server.
- Clean traffic
- 25 TB
- Rate
- $3 / TB
- Protocol
- TCP + UDP
- Origin
- Existing host
Billed monthly
Protection plan
Choose your clean-traffic allowance.
Select the normal traffic your service transfers each month. Traffic blocked during an attack does not count toward this allowance.
Clean traffic allowance
Choose the expected monthly clean traffic.
25TB
5 TB minimum · 100 TB standard maximum.
Billing
Billed monthly.
Monthly only
$3 per TB of clean traffic · 5–100 TB standard range
ServiceClean trafficRateProtocolOriginPrice and setup
Blocked attack traffic is excluded from clean-traffic usage. Approved ports are confirmed before setup.
Traffic path
How protected traffic reaches your server.
Players and clients connect to a Fluxorus protected IP. Traffic on approved ports is filtered, then forwarded to your existing origin.
Designed for game servers, voice services, and other TCP or UDP services.
Websites using HTTP or HTTPS need application-layer protection.
How traffic moves
TCP + UDP
- 01
Public clients
Connect to your Fluxorus protected address.
- 02
Fluxorus network
Filters traffic on the ports approved for your service.
- 03
Origin server
Receives the traffic forwarded to your existing host.
Your server and provider stay in place. Only the public route changes.
Protection setup
Review the route before cutover.
Confirm the origin, protected endpoint, and forwarding rules with the Fluxorus team before users move to the new address.
- 01
Share your origin
Send the public server address and the TCP or UDP ports that need protection.
- 02
Review the route
We confirm the protected endpoint and forwarding rules before traffic moves.
- 03
Complete the cutover
Point users to the protected address and restrict direct origin access where possible.
Route review
Protected endpoint and forwarding rules
Example interface · Final values are confirmed during setup
Protected endpoint
ActivePublic address
203.0.113.42
Documentation address
Forwarding ruleProtocolStatus
30120
Game traffic
30120
Service traffic
25565
Game traffic
Origin and ports confirmed before cutover
Remote protection questions
Before you route traffic.
Review the basics or contact support about your origin, ports, and expected traffic.
The service is designed for supported public TCP and UDP services, including game and voice servers. It is not a replacement for application-layer protection for a public website or other HTTP and HTTPS traffic.
Your monthly allocation is based on traffic that remains after attack traffic is filtered. Traffic blocked as part of an attack does not count against the clean-traffic amount you selected.
Remote DDoS Protection is $3 per TB of clean traffic per month. Standard configurations start at 5 TB for $15 per month and can be configured up to 100 TB on this page.
Yes. The protected address forwards approved traffic to an existing public origin, so the server can remain with its current provider as long as the service can be reached correctly.
Short usage bursts can occur. If clean traffic remains above the selected amount, we will work with you to move the service to a more suitable allocation instead of treating blocked attack traffic as usage.
It becomes the public address for the protected service, but origin privacy also depends on your configuration. Old DNS records, server listings, or unrestricted firewall access can still expose the origin and should be reviewed during cutover.
Yes. Open chat with your expected clean traffic, protocols, and ports so the Fluxorus team can review a custom allocation.
Ready to configure
Choose clean traffic and review the route.
Select a monthly allowance, then share your origin and approved ports with the Fluxorus team.