ixreport

Bridge IX BTR Route Servers: PeeringDB fix list

AS400549 · peeringdb.com/net/29646

PeeringDB

One thing to fix in Bridge IX BTR Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Bridge IX BTR 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 Baton Rouge, LAghost Baton Rouge, United States · PeeringDB 3787
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB216.59.37.249 is AS205529 DE-CIX Monitoring216.59.37.249
    Address belongs to another network in PeeringDB2607:1780:8000:c1d:6:1ca5:c:1 is AS205529 DE-CIX Monitoring2607:1780:8000:c1d:6:1ca5:c:1
    IPv4 address missing from PeeringDB216.59.37.252 216.59.37.253216.59.37.249 216.59.37.252 216.59.37.253 216.59.37.254
    IPv6 address missing from PeeringDB2607:1780:8000:c1d:6:1ca5:a:1 2607:1780:8000:c1d:6:1ca5:a:22607:1780:8000:c1d:6:1ca5:a:1 2607:1780:8000:c1d:6:1ca5:a:2 2607:1780:8000:c1d:6:1ca5:b:dead 2607:1780:8000:c1d:6:1ca5:c:1
    Port speed differs2 × 10G4 × 20G

    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 216.59.37.252: set Speed to 20000 (20G) (now 10000).
    • In the entry with IPv4 216.59.37.253: set Speed to 20000 (20G) (now 10000).
    • Add an entry: IPv4 216.59.37.254, IPv6 2607:1780:8000:c1d:6:1ca5:b:dead, speed 20000 (20G), RS peer no.

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