IP Peering Policy
PowerCloud SP Peering Requirements
PowerCloud SP is willing to peer (IPv4 and IPv6) with networks which are connected to one or more exchange points which we have in common.
If you require a more formal agreement, contact us and we will make arrangements. We will announce to you via BGP4 any routes which we carry and will listen to any routes that you carry. Our peering policy is simple, if you peer with PowerCloud, we expect the following:
- Only send us traffic that is destined for the prefixes we announce to you. Do not point default at us or use static routes to send us traffic that does not match the routes we announce to you.
- PowerCloud SP will generally announce consistent routes at each exchange point and expects peers to generally do the same. We understand that due to submarine cable faults or other reasons you may need to temporarily vary your announcements.
- PowerCloud SP expects you to peer at all exchange fabrics we have in common if we peer with you via public exchanges or all facilities we have in common if we peer via private interconnect with you. In other words, if you are peering in the Capetown, Johannesburg and Kwazulu-Natal at the same locations as PowerCloud you must peer with PowerCloud at all those locations. This is to prevent problems for your and our customers so that customer traffic does not cross provinces twice to return back to the same area.
- PowerCloud SP sets up IPv6 peering (along with IPv4 peering) with all networks that run both protocols.
Network Information (Registered at PeeringDB)
Any network is welcome to contact PowerCloud SP via email at email@example.com to discuss peering. Please include your ASN and peering point locations. An up-to-date peeringDB entry is nearly always required.
|General Peering Information|
|Max Prefix IPv4:||100|
|Max Prefix IPv6:||1|
|Peering Policy||Open (for both IPv6 & IPv4)|
|NAPAfrica IX Johannesburg|
|Port Speed:||10 Gbps|