Peering information

General

Locations: Required — EU

Contracts

Not required for standard IXP peering.

BGP communities

Requirements

• A publicly routable ASN registered in a Regional Internet Registry.
• Up-to-date PeeringDB record with accurate facility and IXP information.
• Presence at a mutually available IXP or facility in the EU.
• Both IPv4 and IPv6 peering sessions where technically feasible.
• Ability to exchange traffic without a mandatory traffic ratio.

Technical

• MD5 authentication supported upon request.
• Maximum prefix limits applied according to PeeringDB values.
• Only send traffic destined to prefixes announced by AS198831.
• Do not point default or static routes toward AS198831 unless agreed.
• IRR AS-SET: AS198831:AS-HOLYCLOUD — filter announcements accordingly.

Operational

• Maintain a responsive NOC reachable 24×7 for network events.
• Notify us of planned maintenance affecting peering sessions.
• Keep PeeringDB and IRR objects current.
• Contracts are not required for standard IXP peering.

Private interconnects

PNIs considered at shared facilities (Paris, Frankfurt, London).