One location, stated plainly
The Templass edge sits in Equinix FR5, Frankfurt. That is where your protected address lands, where attacks are dropped, and where clean traffic leaves toward you. There is no second scrubbing site to guess about. If you need a different campus, ask.
The edge is in the over 1 Tbps mitigation class. That number describes the platform, not what you buy. Your quote is for clean Mbps at the origin.
AS208743
Templass announces protected addresses from its own autonomous system, AS208743. You can look it up in the RIPE database and check routes on the looking glass.
Once you are protected, a traceroute to your service should enter AS208743. If it ends on your origin's transit network instead, the address is leaking or DNS still points at the origin.
Why Frankfurt helps
For European users and European origins, Frankfurt keeps paths short. Latency is the path from the user to Frankfurt plus the path from Templass to your origin. If your server is in Germany or nearby, that second leg stays small even over a tunnel.
If your origin is far from Frankfurt, every clean packet takes that extra stretch. It is worth knowing before you choose where to run the server.
Two ways to connect
- GRE tunnel. For an origin anywhere on the internet. Fast to stand up, no data center order. Details on DDoS protection over GRE.
- Cross-Connect in FR5. A dedicated physical link for customers who colocate in FR5 or can order a circuit into it. Lower latency and no GRE encapsulation, in exchange for Equinix order time. Templass issues the LOA after the quote is accepted.
What happens during an attack
Mitigation is already running on a provisioned service, so an attack does not need a phone call to start. The flood arrives in FR5, Layer 3 and Layer 4 abuse is dropped or limited there, and your origin keeps receiving the clean rate.
In the Panel, Attacks shows whether the event is being recorded, with its vectors, peak rates and status. Firewall and rate-limit rules apply at the same Frankfurt edge if you want to tighten a specific port or source. If humans need to join, open a Ticket from the same account with the protected address, a start time in UTC, and what you are seeing.
The one thing to avoid is leaking the origin. Do not point DNS back at the real server or announce the address on a backup uplink to get around the problem. That turns the backup into the attack path.
Who it suits
- Game servers and Minecraft networks with European players.
- Hosting providers and API origins in or near Frankfurt.
- Racks already in Equinix FR5 that want a physical handoff.
Billing is the same everywhere: clean Mbps at the 95th percentile. See DDoS protection pricing and the network page.