Locations
Templass filters traffic in three locations on AS208743:
| Location | Building |
|---|---|
| Frankfurt | Equinix FR5 |
| London | Telehouse North Two |
| Amsterdam | Databarn |
At each one, attack traffic is filtered inline as it arrives and clean traffic goes on to your server. You can connect with a Cross-Connect in the building, or reach a server anywhere over GRE.
Frankfurt (Equinix FR5)
Users and servers in Europe have a short path here. You can order a Cross-Connect in this building, or reach a server anywhere over GRE.
London (Telehouse North Two)
Pick London on the quote form if you want your traffic filtered here or need a handoff in the building.
Amsterdam (Databarn)
Pick Amsterdam on the quote form if you want your traffic filtered here or need a handoff in the building.
Picking a location
- Latency for your users is their path to the location, plus the path from Templass to your server.
- With GRE, a server far from the location adds that extra distance to every clean packet.
- A Cross-Connect only removes the Templass-to-server hop when your equipment is in the same building.
If you are not sure, tell us where your server is hosted in the quote notes and we will suggest a location.
Upstreams
AS208743 is connected to Tier 1 and Tier 2 carriers, including Arelion, Cogent, Hurricane Electric and RETN, so traffic has more than one way in and out. See ASN AS208743.
What you do in Panel
Watch Dashboard and Attacks. Change firewall or rate limits when you need rules on top of default mitigation.