ixreport

Bridge IX CMH Route Servers: PeeringDB fix list

AS400548 · peeringdb.com/net/29645

PeeringDB

One thing to fix in Bridge IX CMH 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 Bridge IX CMH 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. United States DartPoints Bridge IX Dublinghost Dublin, United States · PeeringDB 3786
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB216.59.36.252 216.59.36.253216.59.36.252 216.59.36.253 216.59.36.254
    IPv6 address missing from PeeringDBnone2607:1780:8000:c64:6:1ca4:a:1 2607:1780:8000:c64:6:1ca4:a:2 2607:1780:8000:c64:6:1ca4:b:dead
    Port speed differs2 × 10G3 × 20G
    • In the entry with IPv4 216.59.36.252: set IPv6 to 2607:1780:8000:c64:6:1ca4:a:1 (now empty); set Speed to 20000 (20G) (now 10000).
    • In the entry with IPv4 216.59.36.253: set IPv6 to 2607:1780:8000:c64:6:1ca4:a:2 (now empty); set Speed to 20000 (20G) (now 10000).
    • Add an entry: IPv4 216.59.36.254, IPv6 2607:1780:8000:c64:6:1ca4:b:dead, speed 20000 (20G), RS peer no.

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