Help Center> Web Application Firewall> User Guide (Kuala Lumpur Region)> FAQs> Service Request/Specification> WAF Instance Specifications Change> What Are the Impacts When QPS Exceeds the Allowed Peak Rate?
Updated on 2024-03-14 GMT+08:00
View PDF

What Are the Impacts When QPS Exceeds the Allowed Peak Rate?

If the QPS specifications you select cannot handle the daily peak traffic of protected website or application services, WAF stops protecting your website. This will cause traffic limiting, random packet loss, automatic bypassing of WAF. As a result, your services may become unavailable, frozen, or respond very slowly for a certain period of time.

The following describes the QPS specifications supported by dedicated WAF instances in different deployments.

  • Normal peak requests for a single instance:
    • Specifications: WI-500. Referenced performance:
      • HTTP services - Recommended QPS: 5,000. Maximum QPS: 10,000.
      • HTTPS services - Recommended QPS: 4,000. Maximum QPS: 8,000.
      • WebSocket service - Maximum concurrent connections: 5,000
      • Maximum WAF-to-server persistent connections: 60,000
    • Specifications: WI-100. Referenced performance:
      • HTTP services - Recommended QPS: 1,000. Maximum QPS: 2,000.
      • HTTPS services - Recommended QPS: 800. Maximum QPS: 1,600
      • WebSocket service - Maximum concurrent connections: 1,000
      • Maximum WAF-to-server persistent connections: 60,000
  • Peak rate of CC attack protection
    • Specifications: WI-500. Referenced performance:

      Maximum QPS: 20,000

    • Specifications: WI-100. Referenced performance:

      Maximum QPS: 4,000