ixreport

Data-Beam Business Solution: PeeringDB fix list

AS150000 · peeringdb.com/net/30488

PeeringDB

3 things to fix in Data-Beam Business Solution's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Data-Beam Business Solution'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 (3)

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. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB185.1.125.128 is AS18428 Mercycat Network185.1.125.128
    IPv4 address in PeeringDB, not in the export185.1.125.86185.1.125.128

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • In the entry with IPv4 185.1.125.86: set IPv4 to (empty) (now 185.1.125.86).
  2. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 103.162.254.25: set Speed to 100000 (100G) (now 10000).
  3. Philippines Maharlika IX Manila, Philippines · PeeringDB 4167
    ProblemPeeringDB hasThe export has
    IPv4 address differs163.223.201.27163.223.201.25
    • In the entry with IPv4 163.223.201.27: set IPv4 to 163.223.201.25 (now 163.223.201.27).

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