MDSTELECOM: PeeringDB fix list

AS269832 · peeringdb.com/net/26292

PeeringDB

One thing to fix in MDSTELECOM's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on MDSTELECOM'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 (1)

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. Venezuela NAPVE CCS Caracas, Venezuela · PeeringDB 4524
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB45.68.88.245.68.88.2 45.68.88.26
    IPv6 address missing from PeeringDB2801:18d::22801:18d::2 2801:18d::26
    • In the entry with IPv4 45.68.88.2: set IPv6 to (empty) (now 2801:18d::2).
    • Add an entry: IPv4 –, IPv6 2801:18d::2, speed 100000 (100G), RS peer yes.
    • Add an entry: IPv4 45.68.88.26, IPv6 –, speed 100000 (100G), RS peer yes.
    • Add an entry: IPv4 –, IPv6 2801:18d::26, speed 100000 (100G), RS peer yes.

    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.

From ixreport.com/net/269832/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.