How to get connected to CVIXP

To connect to CVIXP, the minimum requirement is an autonomous system number (ASN) and some technical requirements.

That given, there are just a few more steps:

  • You need a layer 2 transport connection to Praia
  • Select a switch port best suited to meet your needs: 1 Gigabit Ethernet (1GE) or 10 Gigabit Ethernet (10GE)
  • Request an offer and all necessary paperwork by email to sales (at)

A member of our team will then contact you with all necessary information and paperwork.

After the contract is signed by both sides, the CVIXP support will contact you to implement the ordered services.

If you have any questions, please do not hesitate to contact us! Just mailto sales (at) or call us by phone.

We are more than happy to support you when you need layer 2 transport connectivity, IP transit or data center services. Please have a look at the partner list for more information.

Contact Us


These Technical Requirements (TR) define the ways in which you may or may not make use of the CVIXP services. This document will be regularly reviewed and revised in the light of operational experience to ensure maximum protection of service to CVIXP members. Subsequent versions of this document are effective after 10 working days of having been posted upon the CVIXP website.


Members' use of the CVIXP network shall at all times conform to the relevant standards as laid out in STD0001 and associated Internet STD documents.

Technical Requirements

1. Physical

Ethernet interfaces attached to CVIXP ports shall be explicitly configured with duplex, speed and other configuration settings and shall not be auto-sensing.


2. MAC Layer

2.1 Frames forwarded to CVIXP ports shall have one of the following ethertypes

  • 0x0800 - IPv4
  • 0x0806 - ARP
  • 0x86dd - IPv6

2.2 All frames of a service forwarded to an individual CVIXP port shall have the same source MAC address.

2.3 Frames forwarded to CVIXP ports shall not be addressed to a multicast or broadcast MAC destination address except as follows:

3. IP Layer

3.1 Interfaces connected to CVIXP ports shall only use IP addresses and netmasks (prefix lengths) assigned to them by CVIXP . In particular: 

  • IPv6 addresses (link & global scope) shall be explicitly configured and not auto-configured
  • IPv6 site-local addresses shall not be used

3.2 IP packets addressed to CVIXP peering LAN directed broadcast address shall not be automatically forwarded to CVIXP ports.

3.3 Standard IP MTU size = 1500


4. Routing

4.1 All exchange of routes across the CVIXP network shall be via BGP4(+).

4.2 AS numbers used in BGP4(+) sessions across the CVIXP network shall not be from range reserved for private use.

4.3 All routes advertised shall be aggregated as far as possible.

4.4 IP address space assigned to CVIXP peering LAN shall not be advertised to other networks without explicit permission of CVIXP . All routes advertised across the CVIXP network shall point to the router advertising it unless an agreement has been made in advance in writing by CVIXP and the members involved. All routes to be advertised in a peering session across CVIXP shall be registered in the RIPE or other public routing registry. Members may use more than one ASN for their CVIXP peering provided that each ASN presented shares the same NOC and peering contact details.

5. Forwarding

5.1 Traffic shall only be forwarded to a CVIXP member when permission has been given by the receiving member either: 

  • by advertising a route across the CVIXP network (directly or via the routeserver)
  • or explicitly in writing

5.2 Traffic shall not be routinely exchanged between two CVIXP ports owned by the same CVIXP member.