Looking Glass AS328633

Your IP address: 216.73.217.145
Contact: MikroTikSA Support
Powered by Looking Glass 2.3.1
Help
Command
Parameter
Peering Policy
MikroTikSA Networks (AS328633) — Open Peering Policy
1. Overview
MikroTikSA Networks (AS328633) maintains an Open Peering Policy. We are committed to establishing settlement-free interconnection with reliable networks at common Internet Exchange Points (IXPs) and select facilities to improve routing efficiency, lower latency, and enhance the overall end-user experience for both our customers and the broader Internet community.
2. General Principles
- Settlement-Free: Peering with MikroTikSA Networks is strictly settlement-free (mutual and reciprocal exchange of traffic without financial compensation).
- Open Access: We welcome peering requests from any network that meets our basic technical requirements outlined below.
- Reciprocity: Peers are expected to maintain stable connectivity, appropriate route filters, and keep their PeeringDB records updated.
3. Technical Requirements
To establish a direct BGP peering session with AS328633, prospective peers must satisfy the following technical criteria:
- Autonomous System Number (ASN): The peer must possess a globally unique, publicly routed ASN registered with an appropriate RIR (e.g., AFRINIC, APNIC, ARIN, LACNIC, RIPE NCC).
- Routing Registries (IRR / RPKI):
- All prefixes announced to us must be properly registered in an IRR (e.g., AFRINIC, RIPE, RADb) using an
AS-SET. - Route Origin Authorizations (ROAs) must be valid and kept up to date for all announced prefixes to support RPKI validation (Route Origin Validation).
- All prefixes announced to us must be properly registered in an IRR (e.g., AFRINIC, RIPE, RADb) using an
- BGP Configuration:
- Sessions must run BGP-4 for IPv4 and BGP Multiprotocol (IPv6) where applicable.
- Max-prefix limits must be enforced on both sides to prevent accidental prefix leaks.
- Traffic & Routing Hygiene:
- Peers must filter out bogons, martians, default routes (
0.0.0.0/0and::/0), and any routes originating outside their authorized customer/infrastructure scope. - No transit leakage: Peers must not point static routes, default routes, or use MikroTikSA Networks as a backup transit provider without a formal agreement.
- Peers must filter out bogons, martians, default routes (
4. Interconnection Locations
MikroTikSA Networks is actively present at major data centers and Internet Exchange Points in South Africa, including:
- NAPAfrica (Johannesburg & Cape Town)
- CINX (Cape International Exchange)
- Facilities: Teraco (Isando / Cape Town campuses)
We support both public peering via IXP route servers and direct bilateral sessions (IPv4 and IPv6) at our common points of presence.
5. Network Information
- ASN:
AS328633 - AS-SET:
AFRINIC::AS-MIKROTIKSA-ALL - IPv4 Prefix Ranges:
102.223.104.0/22102.217.184.0/22102.201.228.0/22
- IPv6 Prefix Range:
2c0f:e848::/32
- PeeringDB Profile: peeringdb.com/net/22773
6. Contact Information
For new peering requests, maintenance coordination, or routing issues, please contact our Network Operations Center (NOC):
- Peering Requests & Operations: peering@mikrotiksa.com
- Phone / NOC: +27 83 456 2002