Connectivity overview

Templass sits in front of your origin. Dirty traffic is dropped in Frankfurt. Clean traffic is forwarded in one of two ways:

1. GRE tunnel over the public internet
2. Cross-Connect in Equinix FR5

Both deliver scrubbed packets to your equipment. They differ in where the origin lives, how failover looks, and what Templass has to provision. Pick the handoff on the quote form.

GRE tunnel

A GRE tunnel is a point-to-point overlay. Templass encapsulates clean traffic and sends it to a public IP you control. You decapsulate on a router, firewall, or Linux host and hand packets to the real service.

Choose GRE when:

• The origin is already on the internet
• You can terminate GRE and apply a route for the protected prefix
• You want to start without a data-center order

You wait for an admin-provisioned Templass GRE endpoint (and keys, when used). Setup: GRE tunnel setup.

Cross-Connect / Equinix FR5

A Cross-Connect is a physical circuit in the Equinix Frankfurt FR5 campus. Clean traffic leaves Templass on that circuit instead of a tunnel.

Choose a Cross-Connect when:

• You already colocate in FR5, or you can order presence there
• You want a dedicated Layer 2 path and no GRE overhead
• The quote has scoped a physical handoff

Templass issues LOA and Z-side details after the order is accepted. You do not get cage or circuit identifiers from this documentation. Setup: Cross-Connect / Equinix FR5.

What is the same

• Scrubbing stays in Frankfurt (Equinix FR5)
• The public ASN is AS208743
• Protected addresses are assigned or accepted during onboarding
• Return path and origin hiding still matter. See Routing

What Templass will ask you for

GRE	Cross-Connect
Public IP of your GRE endpoint	Equinix customer identity and FR5 presence
Preferred tunnel inner addressing (if you have a standard)	Port speed you can accept
Who should receive the endpoint and keys	Who should receive the LOA

If you are unsure, start with GRE. A later Cross-Connect is a new quote discussion with [email protected].