MikroTikSA Networks Peering Policy

MikroTikSA is an Internet Service Provider. We operate mainly in the Western Cape region of South Africa, although we do support national clients.

Below is a summary of our overall peering policy:

- We operate an Open Peering Policy.

- We support both public and private peering.

- We do not require a minimum amount of traffic to peer.

- We do not consider traffic ratios to peer.

- We do not require a contract to peer.

- We do not support contracts for public peering.

- We announce only MikroTikSA routes from our network.

- We do peer with route servers.

- We exchange both IPv4 and IPv6 routes.

- We do not do prefix- or AS_PATH-based filtering for peer routes. We rely on 'max-prefix' values for route control. However, for the comfort of our peers, we do not accept (or announce) private or reserved IP address space, private AS numbers and IPv4 routes longer than a /24 or IPv6 routes longer than a /48.

- We encourage our peers to rely on 'max-prefix' values for route control in order to reduce administrative overhead and speed up improvement in routing quality enabled by peering.

- We filter (and drop) traffic sourced from or destined to any private or reserved IP address space, in either direction of the peering session.

- We do not accept customer routes from peers.

- We do not perform uRPF on our peering routers, as these routers do not hold a full BGP table.

- We require that peering sessions be setup directly across the public peering LAN or private peering link.

- We do not support eBGP Multi-Hop peering sessions.

For a list of exchange points and data centre facilities where you can peer with MikroTikSA, please visit our PeeringDB record.