Peering Policy

Karmuz Network (AS209990) supports friendly selective peering. We aim for boring routing and exciting uptime.

Key Points

IPv4 + IPv6 supported
BGP sessions at IXPs and via private interconnect (where available)
We filter, we keep promises, and we answer emails
Prefer RIPE IRR objects and RPKI ROAs when applicable

Policy Details

Requirements

Must Have

  • Route filtering (IRR/RPKI) on both sides
  • NOC/abuse contacts

Recommended

  • Max-prefix limits
  • BFD optional

Policy Knobs

  • Traffic ratios: not strict; talk to us if unusual
  • No default routes accepted
  • No route leaks; we will shut the session if needed
Sessions

BGP: 1x IPv4 + 1x IPv6 session per location

Supports multilateral peering via route servers at IXPs (if applicable)

Private interconnect: case-by-case

Communities

Community support is coming soon. The following is a placeholder structure:

Community Meaning
209990:0:xxxx TBD
209990:1:xxxx TBD
209990:2:xxxx TBD
Operational

Maintenance: Planned changes announced when practical via NOC contact or relevant mailing lists.

Monitoring: We monitor sessions and will reach out if issues are detected.

Depeering: We prefer to talk before depeering. If issues arise, expect a courtesy email first.

Meeting Points

Exchange points where we are present, sourced from PeeringDB.

Failed to load meeting points data

Please try refreshing the page.

Locations

Available peering locations and their connection types.

City Code Type Notes
Amsterdam AMS IXP Speed-IX / FogIXP
Zurich ZRH POP Transit/peering as available
Chicago CHI POP Transit/peering as available
Rotterdam RTM Lab Limited/public services

Get in Touch

For peering requests, please include: ASN, location, IPs, IRR as-set, and preferred session type.

Contact Us