General information

HE.NET ARIN PeeringDB

Peering policy

AS924 practices an open peering policy which means that we peer with everyone who wants to peer with us. While we do not require any kind of written contract, you must follow these rules:

  • Peers may only send traffic from their own and downstream networks to us.
  • Peers must operate a Network Operations Center (NOC) reachable by email.
  • Peers must keep their IRR and registry data up to date at any time.
  • Peers shall enforce a strict routing policy to avoid route leaks.
  • Peers shall aggregate their routes to avoid routing table inflation.

Technical Information

Please note the following preferences and technical information before entering a peering with us:

  • Prefixes shorter than a /24 (IPv4) or /48 (IPv6) will be filtered.
  • Prefixes with private or other invalid ASNs in AS_PATH will be filtered.
  • Prefixes pointing to well-known bogon addresses will be filtered.
  • Prefixes with invalid NEXT_HOP attribute will be filtered.
  • We strongly encourage MD5 authentication for additional security.
  • We support usage of the GRACEFUL_SHUTDOWN community.
  • We configure an individual prefix limit for all peering sessions.

Physical Points of Presence

IXP IPv4 Address IPv6 Address Type
FREMIX 185.1.214.9 2001:7f8:116:ee::9 Physical

Communities

Description Standard Community Large Community
Info: Origin Route
Originated by Cloudie 924:0 924:100:0
Info: Transit Route
Learned from Transit 924:1000 924:110:0
Info: IXP Routes
[::] FREMIX 924:1200 924:120:0