At CubixServ
Protected hosting and FiveM Anti-DDoS proxies, managed through your CubixServ client area.
Explore CubixServ services FiveM · Anti-DDoS
NETWORK & ANTI-DDOS
FiveM protection, designed around your traffic.
A remote protection design for FiveM: separate the connection endpoint, game traffic and origin access before activation.
CubixServHosting, panel and customer support
PeeryxIP transit and upstream filtering · AS213382
Peeryx, our Anti-DDoS partner
Peeryx is our Anti-DDoS provider and partner. CubixServ offers protected hosting and FiveM proxies; Peeryx provides IP transit and its software.
Protected IP transit
Hosting providers, data centers and telecom operators: explore Peeryx Anti-DDoS protected IP transit, BGP connectivity and direct subscription.
BGP · GRE · IPIP · VXLAN Subscribe on Peeryx Subscribe to protected IP transit on peeryx.com, our other partner site. Peeryx manages the plans, contract and billing. Peeryx IP transit plansAnti-DDoS software
Defense Fabric: Anti-DDoS filtering on your infrastructure. Licensing and subscription directly with Peeryx.
Explore Defense Fabric Subscribe to protected IP transit on peeryx.com, our other partner site. Peeryx manages the plans, contract and billing.Filter upstream. Deliver useful traffic.
CubixServ operates your hosting and panel. Peeryx supplies our IP transit and upstream Anti-DDoS layer. The protected protocols and delivery model are defined for your service.
- Your usersConnections from the Internet
- Upstream protectionPeeryx network and filtering
- Your serverCubixServ or an approved external host
Available upstream capacity15 Tbps+
Peeryx publishes 15 Tbps+ available through its transit providers. This is aggregate upstream capacity, not bandwidth reserved for your server or a promise of uninterrupted service.
View the technical sourceProtect the protocols that actually carry your service.
HTTP/TLS connection
Server information and the initial connection use the connect endpoint. FiveM-specific HTTP/TLS filtering must be scoped to this path.
TCP + UDP game traffic
The game endpoint also needs raw TCP/UDP forwarding on the advertised ports. ENet and UDP handshakes do not pass through an HTTP-only proxy.
Voice and resources
Review PMA/Mumble ports and resource downloads separately. A cache or voice relay is included only when specified and tested for your deployment.
A protected entry point needs a protected backend.
Restrict the origin firewall to approved delivery paths. Keep administration separate, review DNS records and remove direct public routes that could bypass the proxy.
Network and transport
L3/L4 filtering addresses network and transport traffic. Application-specific profiles depend on the protocol and selected architecture.
Application controls
HTTP/TLS, game logins and voice traffic have different requirements. A web proxy alone does not protect every game protocol.
Trust only the proxy addresses you control. Broad trusted ranges can bypass application rate limits.
A clear deployment, tested before migration.
Map your endpoints
List the host, IPs, TCP/UDP ports, game version, voice services and current provider constraints.
Choose the delivery
Review a protocol-aware proxy, protected IP transit or a tunnel according to the actual topology.
Secure the origin
Prepare the firewall, trusted proxy ranges, DNS or advertised endpoints, and a rollback plan.
Test and migrate
Check player connections, downloads, voice, reconnects and regional delay before directing public traffic to the new entry point.
Measure the path your players use
A web TCP measurement is not a game-latency measurement. Compare relay delay and application response from your players’ regions using the actual game endpoints.
An existing server can stay in place
Remote protection can keep your current host when its firewall, protocols and clean-traffic delivery allow it. Compatibility is reviewed before activation; there is no promise that every host supports every model.
IP and port rotation
Multiple entry points or endpoint changes require a supported routing design, origin restrictions and reconnect tests. Automatic rotation is not a default feature: its mechanism and availability must be confirmed for the proposed service.
CubixServ
Design protection around your real service.
Tell us your game or application, host, ports and player regions. We will confirm the supported architecture, activation steps and commercial terms before an order.
Discuss my protection
Include your protocols and endpoints in the request; never send passwords or private keys.
Questions before choosing protection
Service bandwidth and contractual commitments are separate.
Does 15 Tbps+ belong to my server?
No. This is the aggregate upstream capacity published by Peeryx through its transit providers. The bandwidth, filtering scope and commitments for your own service are specified separately.
Does protection affect latency?
A proxy or tunnel changes the network path and can add delay. The effect depends on the origin, relay and player region. Test the actual game path before migrating; no fixed ping is promised.
Can I protect a server at another host?
Possibly, after reviewing the exposed protocols, origin firewall and delivery options. A host that cannot restrict direct access may leave a route around the protected entry point.
Does Anti-DDoS replace application security?
No. Keep software updated, control access, validate game events and maintain backups. Upstream filtering does not fix vulnerable scripts or guarantee that every attack is blocked without interruption.
Check the protection scope before migration
Practical answers before you order or move an existing project.
Is protecting the website enough for a FiveM server?
No. FiveM game traffic, resource downloads and administration have different roles. Document the TCP and UDP listeners, protect administrative access and control direct connections to the origin. Test a player joining and downloading resources separately from the website or status page.
Does mitigation capacity describe my server bandwidth?
No. The protection network’s capacity and your service’s allocated network rate describe different things. Review the protocols, traffic limits and responsibilities applicable to your project. Keep reproducible connection tests and incident timestamps so the team can investigate the actual traffic path.
