Upstream mitigation
CosmicGuard · AS215703
Inbound game traffic is scrubbed on CosmicGuard’s mitigation-capable transit path. Large volumetric floods are reduced upstream so they are less likely to overwhelm the path into our Virginia edge.
GameDispo
DDoS protected transit
Minecraft and FiveM traffic on GameDispo uses layered protection: upstream DDoS mitigation, then GameDispo edge filtering, before packets reach the game process.
DDoS protected transit is included on every standard Minecraft and FiveM plan — not a separate upsell SKU. The same layered model is applied for both games: scrub first on the transit path, then filter locally on our Virginia edge.
Traffic is not handed straight from the public internet to your game process. It moves through distinct stages — upstream mitigation, then GameDispo edge filtering — so volumetric noise and remaining junk are handled at different layers.
Upstream mitigation
Inbound game traffic is scrubbed on CosmicGuard’s mitigation-capable transit path. Large volumetric floods are reduced upstream so they are less likely to overwhelm the path into our Virginia edge.
GameDispo edge filtering
On our NIC we run our own native XDP program inline, before the normal receive path. Unwanted packets can be dropped early; allowed flows continue toward the stack and game process. This does not replace upstream mitigation — it filters what still arrives.
Game server
Only traffic that passes the filtering stages reaches the actual Minecraft or FiveM process. The goal is to keep remaining junk and application-shaped abuse off the game runtime whenever possible.
Serious game-hosting and network operators rarely rely on a single box firewall. GameDispo follows the common pattern many providers describe as “scrub first, then filter locally.”
XDP_DROP) instead of continuing into higher-level services.
XDP_PASS) into the normal stack and, if passed,
your game process — with stateful / punched allowances for established sessions.
That split exists because upstream scrubbing is built for scale, while game UDP/TCP sessions need tighter, stateful, application-aware decisions that generic volumetric filters alone often miss.
Upstream scrubbing alone can still leave protocol-aware or lower-rate abuse that looks enough like game traffic to pass a volumetric filter.
Local XDP alone cannot absorb multi-gigabit floods that fill the uplink before packets ever reach the NIC. XDP is a precision filter at the edge — not a substitute for transit-scale volumetric mitigation.
Combining protected transit with an inline native filter addresses both problems — capacity upstream, precision at the edge. Providers and network engineers describe this as clean traffic delivery into a host edge that still runs its own filter stack.
Practical outcomes of the architecture — without marketing guarantees.
Detail for operators who want to know what runs on the path. Same facts as our public security write-up — reorganized for readability.
GameDispo places inbound game traffic on DDoS protected transit via CosmicGuard on AS215703. Large volumetric floods are scrubbed on that mitigation-capable transit path so they are less likely to overwhelm the path into our Virginia edge. CosmicGuard handles the transit-scale scrub; it is part of the upstream protection architecture described on this page.
On our NIC we run an in-house native XDP program inline, before the normal receive path. This is the same class of early-driver filtering operators mean when they talk about XDP/eBPF at line rate. Our XDP layer is the local, game-aware filter for what still arrives after upstream scrubbing — not a replacement for volumetric mitigation.
XDP_DROP
Discard traffic directly at the packet-processing layer.
XDP_PASS
Allow validated traffic to continue through the network stack.
The XDP path keeps flow state and punched allowances (short-lived openings for flows that have already proven legitimate) for game sessions, so real players are not treated like anonymous flood sources after they have established a valid session.
On top of volumetric scrubbing, we apply game-oriented checks — ports, protocol shape, rates, and related state — aimed at traffic that bypasses or survives upstream filtering. The goal is to handle that remainder on the edge at line rate instead of letting it land on your game process.
XDP_DROP or XDP_PASS into the normal stack and, if passed, your game processWe publish the architecture. We do not invent capacity theater.
GameDispo intentionally avoids publishing unverified Tbps capacity, packet-per-second capacity, latency guarantees, attack-size guarantees, or nanosecond marketing numbers. Those figures are easy to print and hard to substantiate in the conditions that matter to your server.
DDoS mitigation reduces attack impact; it cannot guarantee that every attack will have zero impact, or that a service will never experience disruption. Mitigation is not a challenge or “unbootable” guarantee.
Coverage and credits are defined in the SLA. Using protection to bait or advertise attacks is prohibited under the AUP.
Prefer layered, inspectable design over a single slogan. Prefer accurate limits over unverifiable claims.
GameDispo
Virginia · CosmicGuard scrub + inline native XDP · standard plans