asn.dev

Internet exchange

Mozambique Internet Exchange

active Maputo, Mozambique MPM

Recorded members 32 addresses on file
Connected ports 18 across all participants
Peak traffic 14.7 kbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Maputo, Mozambique
Region
Africa
Airport code
MPM
Status
Active
PCH record updated
2016-11-22

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
196.223.33.0/24IPv4Active18
2001:43f8:930:cafe::/64IPv6Active18

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

23 networks · 32 addresses

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. Each network's addresses on the fabric are listed together, IPv4 first. Typing in the box narrows the rows below; Search looks through all 32 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS3491PCCW Global (HK) Ltd.196.223.33.22—Restrictive
AS60171AFR-IX TELECOM S.A.196.223.33.302001:43f8:930:cafe::30——Selective
AS42WoodyNet, Inc.196.223.33.1502001:43f8:930:cafe::150——Open
AS33763Paratus Telecommunications Limited196.223.33.28—Selective
AS63293Facebook, Inc.196.223.33.1492001:43f8:930:cafe::149———
AS328748Agile Solutions Provider (PTY) LTD196.223.33.332001:43f8:930:cafe::33——Selective
AS3856Packet Clearing House, Inc.196.223.33.1512001:43f8:930:cafe::151——Open
AS37697WEBMASTERS, LDA.196.223.33.24—Open
AS37342Movitel, SA196.223.33.19—Open
AS30619Moçambique Telecom, SA - TMCEL - Moçambique Telecom, SA196.223.33.18196.223.33.6——Selective
AS37223Vodacom Mocambique S.A196.223.33.10196.223.33.4——Selective
AS327750JENNY INTERNET (PTY) LTD196.223.33.312001:43f8:930:cafe::31——Selective
AS328223VOIPTECH LIMITADA196.223.33.29—Open
AS31960Eduardo Mondlane University196.223.33.1—Open
AS37436INTIC (National Institute of ICT)196.223.33.26——
AS327700MoRENet - Mozambique Research & Education Network - MoRENet196.223.33.25—Open
AS37110moztel-as196.223.33.15—Open
AS36865Teledata Mozambique196.223.33.14—Selective
AS36945Mocambique Celular, SARL196.223.33.12——
AS37489ABARI COMMUNICATIONS MOZAMBIQUE LDA196.223.33.21——
AS37556Cilix Software196.223.33.23196.223.33.3——Restrictive
AS37047AFRICAN NETWORK INFORMATION CENTRE196.223.33.17——
AS65009INTERNET ASSIGNED NAMES AUTHORITY196.223.33.9——

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-10-11 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,138 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.