At CubixServ
Protected hosting and FiveM Anti-DDoS proxies, managed through your CubixServ client area.
Explore CubixServ services FiveM · Anti-DDoSCubixServ operates your hosting. Peeryx supplies our IP transit and upstream protection. Explore the path, responsibilities and limits.
Peeryx is our Anti-DDoS provider and partner. CubixServ offers protected hosting and FiveM proxies; Peeryx provides IP transit and its software.
Protected hosting and FiveM Anti-DDoS proxies, managed through your CubixServ client area.
Explore CubixServ services FiveM · Anti-DDoSHosting 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 plansDefense 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.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.
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 sourceAt the same bandwidth, smaller frames mean more packets to process. Compare frame sizes and see their link occupancy.
Enter a positive bandwidth up to 20 Tbps, with at most three decimal places.
Untagged Ethernet model: the selected frame size includes FCS. Add 8 bytes of preamble/SFD and the equivalent of 12 bytes for the inter-frame gap. Tunnels, hardware limits and application processing costs are not modeled.
pps = floor(bits/s ÷ ((frame + 20) × 8))CubixServ manages hosted game and VPS services, the panel and customer support. The offer specifies resources and the service location.
Peeryx supplies our IP transit and upstream Anti-DDoS layer. AS213382 is announced by Peeryx, not owned by CubixServ.
Network capacity, game filtering, application controls and customer bandwidth are separate facts. Review the selected offer rather than assuming a universal protection profile.
Restrict the origin firewall to approved delivery paths. Keep administration separate, review DNS records and remove direct public routes that could bypass the proxy.
L3/L4 filtering addresses network and transport traffic. Application-specific profiles depend on the protocol and selected architecture.
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.
List the host, IPs, TCP/UDP ports, game version, voice services and current provider constraints.
Review a protocol-aware proxy, protected IP transit or a tunnel according to the actual topology.
Prepare the firewall, trusted proxy ranges, DNS or advertised endpoints, and a rollback plan.
Check player connections, downloads, voice, reconnects and regional delay before directing public traffic to the new entry point.
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.
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.
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.
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.
Include your protocols and endpoints in the request; never send passwords or private keys.
Service bandwidth and contractual commitments are separate.
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.
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.
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.
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.