ixreport

UNILAB Network: PeeringDB fix list

AS218134 · peeringdb.com/net/44260

One thing to fix in UNILAB Network's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on UNILAB Network'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. South Korea KCIXP Seoul, South Korea · PeeringDB 5098
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone163.61.162.17
    • In the entry with IPv6 2a0b:4e07:fb::17: set IPv4 to 163.61.162.17 (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.

From ixreport.com/net/218134/: 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.