ixreport

Swaziland PTC

AS19711 · Eswatini PTC

8Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
8Using the route servers
8To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Swaziland PTC? · Where should Swaziland PTC peer next? · Compare Swaziland PTC with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

8 things to fix in Swaziland PTC's PeeringDB record, from what its exchanges publish: 8 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Swaziland PTC'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 (8)

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.

  1. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:1::a501:9711:1
    • In the entry with IPv4 80.249.212.89: set IPv6 to 2001:7f8:1::a501:9711:1 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::4cff:0:2
    • In the entry with IPv4 80.81.196.36: set IPv6 to 2001:7f8::4cff:0:2 (now empty).
  3. Portugal DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d5::4cff:0:1
    Port speed differs100M10G
    • In the entry with IPv4 185.1.131.17: set IPv6 to 2001:7f8:d5::4cff:0:1 (now empty); set Speed to 10000 (10G) (now 100).
  4. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:36::4cff:0:1
    • In the entry with IPv4 206.82.104.253: set IPv6 to 2001:504:36::4cff:0:1 (now empty).
  5. South Africa JINX Johannesburg, South Africa · PeeringDB 129
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:1f0::104
    • In the entry with IPv4 196.60.96.104: set IPv6 to 2001:43f8:1f0::104 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  6. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::4cff:1
    Port speed differs1G2G
    • In the entry with IPv4 195.66.225.76: set IPv6 to 2001:7f8:4::4cff:1 (now empty); set Speed to 2000 (2G) (now 1000).
  7. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d1::245
    • In the entry with IPv4 196.60.70.245: set IPv6 to 2001:43f8:6d1::245 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  8. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::30
    • In the entry with IPv4 196.60.8.30: set IPv6 to 2001:43f8:6d0::30 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

02468Oct 3, 2026Nov 19, 20268
Show as a table
DateExchanges
Nov 19, 20268
Nov 18, 20268
Nov 17, 20268
Nov 16, 20268
Nov 15, 20268
Nov 14, 20268
Nov 13, 20268
Nov 12, 20268
Nov 11, 20268
Nov 10, 20268
Nov 9, 20268
Nov 8, 20268
Nov 7, 20268
Nov 6, 20268
Nov 5, 20268
Nov 4, 20268
Nov 3, 20268
Nov 2, 20268
Nov 1, 20268
Oct 31, 20268
Oct 30, 20268
Oct 29, 20268
Oct 28, 20268
Oct 27, 20268
Oct 26, 20268
Oct 25, 20268
Oct 24, 20268
Oct 23, 20268
Oct 22, 20268
Oct 21, 20268
Oct 20, 20268
Oct 19, 20268
Oct 18, 20268
Oct 17, 20268
Oct 16, 20268
Oct 15, 20268
Oct 14, 20268
Oct 13, 20268
Oct 12, 20268
Oct 11, 20268
Oct 10, 20268
Oct 9, 20268
Oct 8, 20268
Oct 7, 20268
Oct 6, 20268
Oct 5, 20268
Oct 4, 20268
Oct 3, 20268

Map

Where Swaziland PTC'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.

Exchanges

Total port capacity 173.1G across 8 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.212.89 2G 73 routes Both IPv6 not in PeeringDB
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.196.36 100G Down Both IPv6 not in PeeringDB
Portugal DE-CIX Lisbon Lisbon, Portugal 185.1.131.17 100M 68 routes Both IPv6 not in PeeringDBSpeed differs
United States DE-CIX New York New York, United States 206.82.104.253 20G Down Both IPv6 not in PeeringDB
South Africa JINX Johannesburg, South Africa 196.60.96.104 10G 73 routes Both IPv6 not in PeeringDB
United Kingdom LINX LON1 London, United Kingdom 195.66.225.76 1G 47 routes Both IPv6 not in PeeringDBSpeed differs
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.245 10G 47 routes Both IPv6 not in PeeringDB
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.30 30G 73 routes Both IPv6 not in PeeringDB

Swaziland PTC lists no facilities in PeeringDB.