# DDoS Mitigation

## Overview

Templass runs a reliable network and reverse proxy service, positioned between your users and servers. We intercept packets, applying our advanced algorithms to assess the legitimacy of incoming traffic to your service. If we detect invalid or malicious activity, Templass promptly mitigates it, ensuring your services stay online.\
\
**3.5+ Tbit/s** Mitigation Capacity\
**2.5+ Tbit/s** Uplink Capacity\
**8 PoPs** Points of Presence\
**99.996%** Uptime Last 3 Months

## **Anycast Technology**

Anycast directs users to our nearest [PoP (Point of Presence)](/features/locations.md), reducing latency and improving response times. It also ensures continuous service availability by redirecting traffic during server failures.

## Protection

**Common Layer 3 (L3) and Layer 4 (L4) DDoS Attacks are Blocked**\
\- ICMP Flood\
\- UDP Flood\
\- SYN Flood\
\- ACK Flood\
\- UDP Reflection/Amplification\
\- Fragmentation Attack

**Common Layer 7 (L7) DDoS Attacks are Blocked**\
\- HTTP Flood\
\- Slowloris\
\- HTTP POST Flood\
\- DNS Flood\
\- SSL/TLS Exhaustion\
\- Botnet Attacks\
\
Templass Protection operates continuously, without requiring Time to Mitigate (TTM). Each incoming packet undergoes thorough inspection to verify compliance with specific application protocols. This stringent checking process ensures that only legitimate packets are forwarded to your server, while any erroneous or invalid packets are promptly blocked at our edge.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.templass.com/features/ddos-mitigation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.