AS202076

Optua Selective Peering Policy

ASN: 202076

PeeringDB: https://www.peeringdb.com/asn/202076

NOC: noc@as202076.net (24×7)

1. General Policy

Optua operates a selective peering policy. We don't peer with everyone just because we share an IXP, but if your network is solid, your routes are clean, and you meet our requirements, we're interested.

We prioritise peering with networks where there's mutual value, whether that's improving performance for our customers, optimising paths, or keeping traffic local.

2. Technical Requirements

  • Routing Protocol: BGPv4 (IPv4) and/or BGPv6 (IPv6).
  • ASNs: Must be publicly registered in a recognised RIR database.
  • Prefix Limits: Sensible maximums in place; see PeeringDB for our current settings.
  • Filtering: IRR-based filtering (RADB, RIPE, ARIN, etc.) and mandatory RPKI ROA validation.
  • Aggregation: Aggregated announcements only, no more specifics than registered in IRR/RPKI.
  • Stability: No route leaks, constant flapping, or misoriginated prefixes.
  • Self-sufficiency: Your network must not require our default route to function.

3. Operational Requirements

  • Contact: Maintain a 24×7 NOC contact who can fix routing issues fast.
  • Maintenance: Give us advance notice if planned work may drop or impact a session.
  • Traffic Quality: No spoofing, abuse, malformed traffic, or anything likely to make security teams twitch.

4. Locations & Route Server Policy

Current IXPs (full list on PeeringDB):

  • LONAP – London, UK
  • LINX LON1 – London, UK
  • LINX LON2 – London, UK

Private peering is available in our core PoPs on request.

Route Server Note: If we're both already on an IXP route server, there's no real need for bilateral peering unless you have a specific technical case (e.g. custom BGP communities, TE, bypassing route server policy).

5. Routing Policy

  • IRR Sources: RIPE, RADB, ARIN, APNIC, AFRINIC.
  • RPKI: Strict validation, invalids are dropped without ceremony.
  • Communities: BGP community controls documented on PeeringDB.
  • Traffic Engineering: We honour MEDs and standard BGP best practices where practical.

6. How to Peer

  1. Check our details on PeeringDB.
  2. Email peering@as202076.net with:
    • ASN
    • IPv4/IPv6 peering IPs
    • Max prefixes you plan to advertise
    • Peering location(s)
  3. If we see a good case for it, we'll usually get you set up within 2–3 business days (faster if the coffee's strong).

7. Exceptions & Suspensions

We may:

  • Decline peering where there's no clear mutual benefit.
  • Suspend a session for operational/security reasons.
  • Apply shaping or filtering during abuse/attack events.
  • End peering if policy violations or instability persist.

Bottom Line

We'll happily peer with stable, well-run networks that bring value to both sides. But if your routes are messy or you treat BGP like a junk drawer, it's a no.