At a Glance

Peering Policy & Requirements

If you want to peer with me, you're welcome! My peering policy is generally open, but I do have a few expectations to ensure a smooth and secure connection:

• Technical contact information must be kept up-to-date.
• Strict route filtering must be enforced to prevent accidental route leaks.
• We should collaborate in troubleshooting peering issues, actively mitigating DDoS attacks, and resolving security incidents.
• Please do not abuse the peering link by pointing default routes or unnecessarily resetting next-hops.

How to Request Peering

If you're interested in peering, just send an email with the following details about your network to get started:

• A short introduction to your network (just so I know who I'm connecting with!)
• Desired peering points (e.g., IPv6-in-IPv4 tunnel, GRE, or LocIX)
• Your Autonomous System Number (ASN)
• Your AS-SET (if you have one)
• The recommended maximum prefix limit I should configure for you
• Your contact details

You can send your peering requests directly to peering@hofstede.it.

Routing Security

• Prefixes I accept must be RPKI: Valid or Undefined. Valid IRR entries are the bare minimum.
• My prefix is covered by a ROA (origin AS201379, max length /48) and by route6 and as-set objects in the RIPE database.

Prefixes

I only do IPv6, as it's the modern internet standard.

• 2a06:9801:1c::/48 IPv6 Only

Upstream / Transit

• AS209735 – Lagrange Cloud Technologies Limited
• AS207841 – Inferno Communications Ltd
• AS34872 – Servperso Systems
• AS34927 – iFog GmbH
• AS20473 – The Constant Company, LLC
• AS41051 – Freetransit Project (Openfactory GmbH)
• AS212895 – Johannes Ernst / Route64.org

Internet Exchange Points

I peer with the route servers at LocIX Düsseldorf, FogIXP and EVIX (Fremont and Amsterdam) and currently maintain over 100 peering sessions across these exchanges.

Direct Peers

• AS24940 – Hetzner Online GmbH

More Information