AS218928
  • Network
  • Peering
  • Contact
  • Impressum

Peering Policy

General Requirements

  • publicly routable ASN and IPv6 Prefix
  • up-to-date PeerinDB entry
  • up-to-date NOC and peering contacts

Technical Requirements

  • sessions are implemented with BGP version 4
  • sessions should be established over IPv4 and IPv6, if available
  • maximum-prefixes should be documented in PeeringDB and should never be exceeded
  • no routes learned from transit or other peerings may be advertised to AS218928
  • no default route may be advertised to AS218928
  • no static routes to AS218928 may be used
  • for IXPs with AS218928 presence see our PeeringDB entry

Peering at IXP

  • for IXPs with AS218928 presence see our PeeringDB entry
  • AS218928 peers with route-servers (RS) and prefers omitting additional direct sessions to peers
  • direct sessions may be established if the peer does not peer with RS or if direct sessions bring other benefits (e.g. additional routes that are not announced to RS)

Private Network Interconnects

  • PNIs are possible in our Frankfurt PoP
  • PNIs are subject to availability and economic feasibility of crossconnects and ports
  • available interface types are 10GBASE-LR
  • traffic levels must justify the requested interface type
  • crossconnects must be singlemode fiber

General Policy

  • dvertisements with extraordinary attributes (e.g. very long as-path) may be dropped
  • AS218928 may alter the peering policy and peering requirements at any time
  • AS218928 may accept or decline a peering request at any time for any reason
  • AS218928 may suspend peering (e.g. in case of connectivity issues, debugging, or maintenance) without prior notice
  • AS218928 may terminate any peering connection at any time without notice

Thank you for Peering!

If you want to peer with AS218928, please send us an email and include your peering details.


© Carl Fischer 2026 | hugo.386 theme by Max le Fou | Powered by Hugo

PeeringDB BGP.tools bgp.he.net