ZAP-Angola
AS37645 · ZAP
Tools: Where can I peer with ZAP-Angola? · Where should ZAP-Angola peer next? · Compare ZAP-Angola with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
5 things to fix in ZAP-Angola's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on ZAP-Angola's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (5)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Port speed differs 1G 100G - In the entry with IPv4 80.81.195.187: set Speed to 100000 (100G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 100G - In the entry with IPv4 185.1.131.61: set Speed to 100000 (100G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 100G - In the entry with IPv4 185.1.192.134: set Speed to 100000 (100G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 196.60.71.99: set Speed to 10000 (10G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 196.60.11.59: set Speed to 10000 (10G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 15 |
| Nov 18, 2026 | 15 |
| Nov 17, 2026 | 15 |
| Nov 16, 2026 | 15 |
| Nov 15, 2026 | 15 |
| Nov 14, 2026 | 15 |
| Nov 13, 2026 | 15 |
| Nov 12, 2026 | 15 |
| Nov 11, 2026 | 15 |
| Nov 10, 2026 | 15 |
| Nov 9, 2026 | 15 |
| Nov 8, 2026 | 15 |
| Nov 7, 2026 | 15 |
| Nov 6, 2026 | 15 |
| Nov 5, 2026 | 15 |
| Nov 4, 2026 | 15 |
| Nov 3, 2026 | 15 |
| Nov 2, 2026 | 15 |
| Nov 1, 2026 | 15 |
| Oct 31, 2026 | 15 |
| Oct 30, 2026 | 15 |
| Oct 29, 2026 | 15 |
| Oct 28, 2026 | 15 |
| Oct 27, 2026 | 15 |
| Oct 26, 2026 | 15 |
| Oct 25, 2026 | 15 |
| Oct 24, 2026 | 15 |
| Oct 23, 2026 | 15 |
| Oct 22, 2026 | 15 |
| Oct 21, 2026 | 15 |
| Oct 20, 2026 | 15 |
| Oct 19, 2026 | 15 |
| Oct 18, 2026 | 15 |
| Oct 17, 2026 | 15 |
| Oct 16, 2026 | 15 |
| Oct 15, 2026 | 15 |
| Oct 14, 2026 | 15 |
| Oct 13, 2026 | 15 |
| Oct 12, 2026 | 15 |
| Oct 11, 2026 | 15 |
| Oct 10, 2026 | 15 |
| Oct 9, 2026 | 15 |
| Oct 8, 2026 | 15 |
| Oct 7, 2026 | 15 |
| Oct 6, 2026 | 15 |
| Oct 5, 2026 | 15 |
| Oct 4, 2026 | 15 |
| Oct 3, 2026 | 15 |
Map
Where ZAP-Angola's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| Angola IXP Luanda, Angola | 2 × 10G | Both | |
| angonix Luanda, Angola | 2 × 20G | PeeringDB | |
| DE-CIX Frankfurt Frankfurt, Germany | 1G | Both Speed differs | |
| DE-CIX Lisbon Lisbon, Portugal | 1G | Both Speed differs | |
| DE-CIX Madrid Madrid, Spain | 1G | Both Speed differs | |
| ESpanix Madrid Lower LAN Madrid, Spain | 1G | PeeringDB | |
| FL-IX Miami, United States | 10G | Both | |
| Frys-IX Fryslân, Netherlands | 10G | Both | |
| GigaPIX - LAN 1 Lisbon, Portugal | 10G | Both | |
| IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil | 100G | PeeringDB only | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 20G | PeeringDB only | |
| IXPN Lagos Lagos, Nigeria | 100G | Both | |
| LINX LON1 London, United Kingdom | 1G | Both | |
| NAPAfrica IX Cape Town Cape Town, South Africa | 100G | Both Speed differs | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 100G | Both Speed differs |
These exchanges have a switch in a facility where ZAP-Angola lists itself in PeeringDB, but don't have ZAP-Angola as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| JINXJohannesburg, South Africa | 215 | |
| NetIXSofia, Bulgaria | 204 | |
| Equinix MiamiMiami, United States | 175 | |
| CINXCape Town, South Africa | 128 | |
| NAPAfrica MAPS JohannesburgJohannesburg, South Africa | 31 | |
| JumboIX PeruLima, Peru | 27 | |
| GigaPIX - LAN 2Lisbon, Portugal | 19 | |
| Equinix LisbonLisbon, Portugal | 18 | |
| MegaIX MiamiMiami, United States | 10 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| PIT - LATAM InterconnectMiami, United States | 5 | |
| GNM-IX USNew York, United States | 4 | |
| JINX VoiceJohannesburg, South Africa | 4 | |
| Any2FloridaMiami/Orlando, United States | 2 |
Facilities (7)
The buildings ZAP-Angola lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix MI1 - Miami, NOTAMiami | 1 of 9 | |
| Teraco Johannesburg Campus, South AfricaJohannesburg | 1 of 6 | |
| Equinix LS1 - LisbonLisbon | 2 of 5 | |
| Teraco CT1 Cape Town, South AfricaCape Town | 1 of 3 | |
| AngoNAP FortalezaFortaleza | 1 of 2 | |
| AngoNAP LuandaLuanda | 1 of 1 | |
| Paratus ITA-DC2Luanda | 1 of 1 |