PacketsDecreaser Docs
PacketsDecreaser Docs
  • ℹ️Informations
    • Location
  • DDoS Protection
    • Informations
    • Layer 4
      • How we mitigate DDoS Attacks
        • Pre-Filter
        • Generic Filter
        • Additional Mitigation Techniques
        • Time to Mitigate
      • Known technical impact
      • Application Filters
        • Wireguard
        • OpenVPN
        • SSH
        • Teamspeak 3
      • Gamefilters
        • FiveM
          • FiveM Layer 4
          • FiveM Layer 7
        • Minecraft Java
        • Valve Source Engine
        • SCP: Secret Laboratory
        • Minecraft Bedrock
        • BeamNG MP
        • Rust
        • Factorio
        • Palworld
      • TCP-Track
    • Layer 7
      • Informations
      • Getting Started
      • SSL Guide
      • How we mitigate DDoS Attacks
        • Edge
        • Filter
        • Clean Proxy
  • Remote DDoS Protection
    • GRE Tunnel
    • Wireguard Tunnel
  • KVM vSERVER
    • Known technical impact
    • Storage vServer
      • Add Storage
      • Upgrade Storage
  • 🕹️Gameserver
    • Information
    • Gamechanger
    • Supported Games
Powered by GitBook
On this page

Was this helpful?

  1. DDoS Protection
  2. Layer 7

Informations


Under normal conditions, the filtering and mitigation process completes within less than 5 seconds, ensuring minimal impact on legitimate users.

However, during extremely large-scale DDoS attacks, the edge may temporarily become overloaded. In such scenarios, mitigation can take up to 60 seconds to fully block malicious traffic.

If an attack reaches several hundred thousand requests per second (RPS), the affected website may experience temporary downtime. During this time, the system is actively analyzing the traffic and beginning the mitigation process in the background. Once enough attack patterns are identified, the system begins blocking malicious IPs, and the attack is mitigated at Layer 4, eliminating further load on the edge.

Important Characteristics:

  • The longer an attack persists, the more effective the mitigation becomes.

  • Short, high-volume bursts may not be fully mitigated during their short runtime, which may result in the edge not responding temporarily. This does not mean mitigation has failed, but rather that the system requires time to react.

  • Over time, even short attacks are detected and mitigated.

  • Frequent attacks help the system learn and improve its mitigation strategy, resulting in faster response with each subsequent attempt.

This adaptive behavior ensures that while initial response time may vary during massive spikes, the system ultimately neutralizes all forms of attack efficiently and with minimal long-term impact. Note: Cloudflare or other CDNs may not work due to the Permanent Mitigation on the Edge. Please do not open any tickets about issues with Cloudflare or other CDN services.

PreviousLayer 7NextGetting Started

Last updated 22 days ago

Was this helpful?