Use Cases
Review the configuration priorities for different services using DDoS protection.
DDoS protection is relevant to services that must remain available over the public internet. Choose a configuration based on protocols, normal traffic, latency requirements, attack history, and recovery objectives—not the industry label alone.
Focus on persistent connections, UDP or custom protocols, packet rate, and latency.
- Confirm that the plan supports the application protocol.
- Match origin rules to the game service's listening ports.
- Test login, matchmaking, and real-time connections before switching production traffic.
- Avoid access-control rules that block legitimate users behind shared egress IPs.
Focus on HTTP/HTTPS, domains, certificates, proxy ports, and origin capacity.
- Configure the correct domain and origin for HTTP/HTTPS forwarding.
- Verify Host handling, TLS certificates, and origin firewall rules.
- Apply application-side rate limits to costly login, search, and API endpoints.
- Avoid exposing the origin IP through DNS, response content, or other services.
Focus on change risk, observability, and recovery procedures.
- Make onboarding and policy changes during a low-traffic window.
- Keep the previous DNS, origin, and policy configuration for rollback.
- Monitor attack statistics, traffic trends, and origin logs.
- Include payment, order, and callback paths in end-to-end testing.
Promotions, launches, and events can increase legitimate traffic quickly.
- Confirm plan specifications and billing rules in advance.
- Use historical data to estimate normal peaks.
- Verify origin capacity and rollback procedures before the event.
- Avoid unnecessary access-control or origin changes during the event.
Confirm Before Choosing a Plan
Protocols and Ports
Onboarding
Identify TCP, UDP, HTTP, HTTPS, and all listening ports used by the service.
Normal Traffic
Capacity
Record normal bandwidth, packet rate, concurrency, and business peaks.
Origin Capacity
Forwarding
Confirm origin capacity, firewall rules, certificates, and health.
Costs and Limits
Plan
Confirm protection specifications and potential charges from the plan, order, and billing terms.
These use cases help define requirements; they do not imply industry-specific protection, fixed capacity, or response commitments. Refer to your plan and agreement for actual capabilities.