VoIP-IX BGP Peering Policy

1. General Overview:

This BGP peering policy outlines the requirements and expectations for establishing BGP peering with other networks at VoIP-IX.net. The goal of this policy is to ensure reliable and efficient routing between our network and other networks.

2. BGP Peering Requirements:

2.1. IP Addressing:

Before establishing BGP peering, each member will be assigned a unique, valid public IP address by VoIP-IX.net. Members are responsible for ensuring that their BGP router is configured with the assigned IP address.

2.2. BGP Version:

Both parties must use compatible BGP protocol versions. We recommend using the latest version of BGP that is supported by all parties.

2.3. AS Numbers:

Each party must have a unique and valid Autonomous System (AS) number. This number must be registered with a recognized Internet registry such as:

African Network Information Center (AFRINIC)
American Registry for Internet Numbers (ARIN)
Asia-Pacific Network Information Centre (APNIC)
Latin American and Caribbean Internet Addresses Registry (LACNIC)
Réseaux IP Européens Network Coordination Centre (RIPE NCC)
2.4. Routing Policies:

Each party must define and implement their routing policies. These policies must be agreed upon by both parties and must not conflict with each other. The policies should include:

The list of prefixes to be advertised and received
The maximum number of prefixes that can be advertised and received
The preferred path for inbound traffic
The preferred path for outbound traffic
The use of community attributes
2.5. Security:

Both parties must implement security measures to protect their BGP peering connections. These measures may include access lists, authentication mechanisms, and encryption. VoIP-IX.net reserves the right to perform periodic checks on the MAC address of the member's equipment to ensure that it matches the registered equipment on record.

2.6. Member's Requirements:

In addition to the above requirements, members must also meet the following criteria:

Have a public Autonomous System (AS) number from the RIPE region
Have up-to-date PeeringDB and RIR Whois information
Have at least one IPv4 /24 or IPv6 /48 to announce
Be able to use the route servers available
Only send traffic to destinations advertised by BGP on the Peering LAN
Will not advertise or export the VoIP-IX.net prefixes externally

2.7. Route Server:

VoIP-IX.net offers the possibility to its members to peer with one or two route servers. The route server allows members to reduce the number of BGP peering sessions required to peer with other members on the exchange. Instead of peering directly with every member, a member can peer with the route server and receive the BGP routes from all other members peering with the route servers.

The route servers IPv4 are:


The route servers IPv6 are:

::/xxThe VoIP-IX.net BGP ASN is:


2.8. Quality of Service (QoS):

VoIP-IX.net applies specific QoS rules for VoIP traffic to ensure high-quality voice communications by prioritizing VoIP traffic over other types of traffic.

VoIP-IX.net monitors the network and may adjust QoS rules as necessary to ensure the highest quality of VoIP traffic.
Members are expected to adhere to these QoS rules to ensure the smooth operation of the exchange and the quality of VoIP communications.

2.9. Open Policy:

VoIP-IX.net has an open peering policy, which means that we welcome peering requests from any interested party that meets our peering requirements. We believe in the importance of open peering to promote the growth and stability of the Internet.

To request peering with VoIP-IX.net, interested parties should contact our peering team and provide the following information:

IP addresses to be announced
Peering policy (including prefix limits, filtering, etc.)
PeeringDB entry
We will evaluate each request based on our peering requirements and network topology. If the request is accepted, we will work with the party to establish BGP peering.

We encourage members to engage with us to ensure that we continue to meet the changing needs of the Internet and to promote the growth of the global network.

2.10. Default Route:

Members must not point a default route to VoIP-IX.net.
Members must send traffic to prefixes that are being advertised by members exclusively.

3. BGP Peering Configuration:

3.1. Physical Connectivity:

The physical connectivity between the two BGP routers must be established before configuring BGP peering.

3.2. BGP Peering Parameters:

The following BGP peering parameters must be configured on both sides:

The IP address of the neighbor router (assigned by VoIP-IX.net or route server)
The AS number of the neighbor router
The BGP version to be used
The routing policies to be implemented
3.3. BGP Peering Monitoring:

BGP peering must be monitored regularly to ensure that it is functioning properly. Monitoring should include:

Tracking the number of BGP prefixes received and advertised
Checking the BGP peering status
Analyzing BGP logs for errors or anomalies

4. BGP Peering Troubleshooting:

If there are issues with BGP peering, both parties should work together to troubleshoot the problem. This may include checking the BGP configuration, monitoring logs, and performing tests.

5. Conclusion:

This BGP peering policy is intended to ensure the reliable and efficient routing between our network and other networks at VoIP

cloud-syncearthbullhorn linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram