Peering
Open Peering Policy
bgp43 has an open peering policy for networks that want settlement-free BGP peering over a dedicated tunnel or at an IXP where bgp43 is already connected. We do not provide tunnel access into an IXP fabric.
Where we peer
- Tunnel peering means a private BGP session with bgp43 over GRE, SIT, WireGuard or VXLAN.
- IXP peering means a BGP session on an IXP LAN where bgp43 already has its own port and address.
- Route-server sessions are treated as IXP sessions and do not use BIRD prefix limits.
What we do not provide
- We do not give customers tunnel-based access to any IXP.
- We do not assign IXP LAN addresses to tunnel users.
- A peering request is only for a BGP session with bgp43, not for remote membership or transport into an exchange.
Import policy
- We build import filters from the peer AS-SET, using PeeringDB IRR data when no AS-SET is entered manually.
- RPKI, bogon, ASN bogon, AS path length and ASPA checks remain active where applicable.
- For bilateral peers we expect the first AS in the path to match the neighbor ASN.
Export policy
- Peering sessions receive either no export or the bgp43 customer cone.
- A peer AS-SET is never added to the bgp43 AS-SET, because the relationship is not downstream transit.
- Default route and full-table export are not used for peering sessions.
Prefix limits
- Bilateral peer sessions use a prefix limit from PeeringDB or an administrator override.
- IXP route-server sessions are configured without import prefix limits.
- If PeeringDB values are missing, the platform falls back to the project default for peer sessions.
IXP
Where bgp43 is present
These are bgp43 router-side IXP attachments. They are listed only for creating BGP peering sessions with bgp43 on that fabric; they are not tunnel access points and their IXP LAN addresses are not assigned to users.
| IXP | Country | City | Datacenter | Router | Our IPv4 | Our IPv6 | PeeringDB IX ID |
|---|---|---|---|---|---|---|---|
| 3am.network Amsterdam, Netherlands / Qupra DC1 | Netherlands | Amsterdam | Qupra DC1 | amsterdam-1 | 91.213.211.77 |
2001:7f8:17d::77 |
5023 |
| Kawaii-IX Amsterdam Amsterdam, Netherlands / Qupra DC1 | Netherlands | Amsterdam | Qupra DC1 | amsterdam-1 | 195.60.92.83 |
2602:f93b:1a35:1311::83 |
4973 |
Peering
Request peering
Create a peering session from the manager, or send your ASN, AS-SET, preferred tunnel peering type or bgp43 IXP presence, and expected route count. Do not request IXP LAN addresses or tunnel access to an IXP; that is not provided.