Usage Policy

Each entity must have a valid non private AS number (ASN attributed by a registry).
The entity should run a related Internet business. Entity should also be able to provide to MA-IX a 24/7 contact.

MA-IX doesn't coordinate peering between members and won't act as a third party in peering relationships or negotiations.

The MA-IX administration reserves itself the right to interrupt the connectivity (temporarily or definitely) of any of its members if one of the following events occurs:

Failure to comply with the rules.
Maintenance purposes.
Statutory obligation from a regulatory authority.
Any issue that would require MA-IX to interrupt connectivity for the respect of others members.

MA-IX is not responsible for any loss or any operational issue generated by any disruption in the MA-IX's services.
The service is provided as it is, without any explicit or implied warranty.

Each members are responsible to interconnect their network with MA-IX, each wire should be labelled (company name, ASN, IP), as clean as possible.

Only BGPv4 is allowed and mandatory as a routing protocol.

The entity should have a registered public ASN to one of the five routing registries.

MA-IX only accepts peering traffic from its members, meaning:

No charged peering traffic.
No next-hop rewrite hack.
No default routes nor statics.

The entity should always send aggregated routes when possible.
Only RIR (RIPE NCC, ARIN, APNIC) registered prefixes shall be announced by members (no RFC 1918 prefixes are permitted).
Minimum length for an IPv4 prefix to be announced is /24.

The protocols below are forbidden on MA-IX:

No discovery protocol (CDP, EDP, IRDP).
No L2 resiliency protocol (VRRP, HSRP or such).
No VTP, GVRP.
No ICMP redirect.
No BootP/DHCP.
No multicast protocols PIM SM/DM/SDM,IGMP.
No IPv6