Nelson Mandela Bay Internet Exchange - NMBINX

South Africa

City
Gqeberha

About this IXP

Data last updated November 2025

Capacity at this IXP

140 Gbps

Cumulative port speeds of all IXP members. This shows the potential maximum traffic that can be exchanged at this IXP at one time.

Membership and capacity

The size and strength of an IXP is determined by a combination of how many members it has, and the total capacity. Larger networks tend to bring more capacity, which can benefit all members.

Data for Nelson Mandela Bay Internet Exchange - NMBINX as shown in PeeringDB in November 2025

Members of this IXP

11

ASNs (autonomous system numbers) are listed in PeeringDB

In the last 12 months

  • ASNs left0
  • New ASNs joined0

Participates in the MANRS IXP program

Yes

IXPs that join this voluntary program apply a framework of enhanced routing security in peering. It signals an extra commitment to responsible Internet stewardship.

Source: MANRS

RIPE Atlas anchor

No

Organizations that run IXPs can host anchors to measure Internet connectivity and traffic. An anchor is a large capacity probe often used by IXPs.

Source: RIPEStat

Member information

Last sync from PeeringDB: November 2025

View this IXP on PeeringDB

Countries of registration

A summary of member registrations by country. An IXP with a mixture of international and near-neighbor members can indicate that an IXP is influential, or acts as a hub within its region or sub-region.

  • South Africa: 6
  • Mauritius: 2
  • United States of America: 2
  • United Kingdom: 1

Types of network at this IXP

The mix of members is an indication of a strength or focus of an IXP.

  • Non-Profit: 3
  • Cable/DSL/ISP: 2
  • Educational/Research: 2
  • Route Collector: 2
  • Enterprise: 1
View all network types
  • Route Server: 1

Members peering at the route server

10 / 11

The route server is a central hub that makes it easier for all networks to peer without having to create individual agreements with other members.

Members using RPKI

9 / 11

members at this IXP use Resource Public Key Infrastructure (RPKI), a security measure that helps ensure traffic is routed correctly. A member is counted as using RPKI if they have at least one valid ROA.

Peering policies of IXP members

Members of an IXP can choose how they peer with others. The Internet Society encourages open policies where possible.

Member list for Nelson Mandela Bay Internet Exchange - NMBINX

This list uses the data available in PeeringDB, which is based on self-reported data, and was last updated in Pulse November 2025

Name AS Number Peering policy RPKI Enabled
AFRINIC DNS Support
  • Autonomous system (AS) number: 37177
  • Type of AS: Non-Profit
  • Peering policy: Open
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Mauritius
  • Total peering locations for this AS: 13
37177 Open Yes
AFRINIC RFC5855 Service
  • Autonomous system (AS) number: 37181
  • Type of AS: Non-Profit
  • Peering policy: Open
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Mauritius
  • Total peering locations for this AS: 13
37181 Open Yes
Amobia Communications
  • Autonomous system (AS) number: 37266
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: South Africa
  • Total peering locations for this AS: 4
37266 Unknown Yes
BGP.Tools Route Collector
  • Autonomous system (AS) number: 212232
  • Type of AS: Route Collector
  • Peering policy: Open
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: United Kingdom
  • Total peering locations for this AS: 123
212232 Open Yes
NMBINX Operations/Route Collector
  • Autonomous system (AS) number: 329234
  • Type of AS: Route Collector
  • Peering policy: Unknown
  • Port speed: 20 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: South Africa
  • Total peering locations for this AS: 1
329234 Unknown Yes
NMBINX Route Servers
  • Autonomous system (AS) number: 37735
  • Type of AS: Route Server
  • Peering policy: Unknown
  • Port speed: 20 Gbps
  • Does this member peer at the route server?: No
  • Country of registration: South Africa
  • Total peering locations for this AS: 1
37735 Unknown No
PCH AS3856
  • Autonomous system (AS) number: 3856
  • Type of AS: Educational/Research
  • Peering policy: Open
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: United States of America
  • Total peering locations for this AS: 316
3856 Open Yes
PCH AS42
  • Autonomous system (AS) number: 42
  • Type of AS: Educational/Research
  • Peering policy: Open
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: United States of America
  • Total peering locations for this AS: 322
42 Open Yes
Vumatel
  • Autonomous system (AS) number: 328829
  • Type of AS: Enterprise
  • Peering policy: Unknown
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: South Africa
  • Total peering locations for this AS: 8
328829 Unknown Yes
ZANOG
  • Autonomous system (AS) number: 328365
  • Type of AS: Non-Profit
  • Peering policy: Unknown
  • Port speed: 20 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: South Africa
  • Total peering locations for this AS: 4
328365 Unknown No
ZTEL
  • Autonomous system (AS) number: 328760
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: South Africa
  • Total peering locations for this AS: 3
328760 Unknown Yes