Billed
Clean delivered bandwidth
What survives scrubbing and reaches your origin.
The attack hits your uplink.Then it hits the invoice.
You run the box people flood. Game servers, hosting, APIs. Volumetric junk saturates the NIC. Application-layer noise burns CPU. Players drop. Tickets pile up.
Most mitigation charges the wrong thing.
A flat fee ignores attack size. A bill for filtered garbage punishes you for being attacked. Templass does neither. You pay for clean bandwidth that actually reaches your origin.
Not billed
Dropped attack traffic
Junk that dies at the edge never hits the invoice.
None
Flat fee on attack size
No fee that scales with how hard you got hit.
Always-on scrubbing at the edge. The invoice tracks what we forward, not what we discard.
Path, network, and the number.
Home is the invoice. Use the other pages for the path, the ASN, and how we meter.
How it works
Internet hits a prefix we announce. We scrub. Clean traffic leaves over GRE or a Cross-Connect.
See the pathNetwork
Own ASN. Frankfurt PoP. Capacity class of the edge. Registry and looking glass live on that page, not here.
Network factsPricing
Clean Mbps at the 95th percentile. Attack volume is not a line item. What we need to quote is listed there.
How billing worksPartners
Connectivity, hardware, and ops around this edge.
Tell us the use case, peak clean Mbps, and how you want to connect. We come back with a number, not a slide deck.
Request a quote