ixreport

4b42 Internet Exchange Point Route Servers: PeeringDB fix list

AS35708 · peeringdb.com/net/19634

PeeringDB

One thing to fix in 4b42 Internet Exchange Point Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on 4b42 Internet Exchange Point Route Servers'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. ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.125.1185.1.125.1 185.1.125.2 185.1.125.3 185.1.125.4
    IPv6 address missing from PeeringDB2001:7f8:d0::8b7c:12001:7f8:d0::8b7c:1 2001:7f8:d0::8b7c:2 2001:7f8:d0::8b7c:3 2001:7f8:d0::8b7c:4
    • Add an entry: IPv4 185.1.125.2, IPv6 2001:7f8:d0::8b7c:2, RS peer yes.
    • Add an entry: IPv4 185.1.125.3, IPv6 2001:7f8:d0::8b7c:3, RS peer yes.
    • Add an entry: IPv4 185.1.125.4, IPv6 2001:7f8:d0::8b7c:4, RS peer yes.

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