Skip to main content

ASN AS208743

Templass operates public autonomous system AS208743. Traffic that users send to your protected addresses is delivered toward this ASN, scrubbed in Frankfurt, then forwarded to your origin over GRE or a cross-connect.

Why the ASN matters to you​

  • Lookups (whois, RIPE Stat, traceroute) should show AS208743 on the Templass-facing path, not your origin ASN, for the protected prefix.
  • Abuse and routing mail for Templass space is handled by Templass, not by your origin provider.
  • Peering and transit on AS208743 are Templass operational details. You do not configure them in Panel.

Public registry data for the ASN lives in RIPE. A convenient view is RIPE Stat for AS208743. Registry objects can change. Treat RIPE as the source for whois fields, not this paragraph.

What you announce​

Most customers do not announce AS208743 themselves.

  • Templass assigns a protected host or prefix and announces it (or otherwise routes it) on AS208743.
  • Your job is to accept that traffic on the GRE tunnel or FR5 cross-connect and to keep the origin from answering the same prefix on another path.

If you need to bring your own prefix or run BGP, that is a Custom discussion with [email protected]. Do not assume BGP sessions, communities, or a looking glass exist until Templass writes them down for your account.

Checks you can run​

After cutover:

  1. whois / RIPE Stat on <PROTECTED_PREFIX> should align with Templass, not with a leftover assignment.
  2. Traceroute from an off-net host should enter AS208743 before it reaches your origin.
  3. Your origin should see traffic arriving from the tunnel or cross-connect, not from a random public default route.

If traceroute still dies on your old ISP path, DNS or the prefix is not on Templass yet.