Booking.com: PeeringDB fix list

AS43996 · peeringdb.com/net/5320

PeeringDB

4 things to fix in Booking.com's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Booking.com'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 (4)

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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs20G30G
    • In the entry with IPv4 80.249.210.198: set Speed to 30000 (30G) (now 20000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs20G30G
    • In the entry with IPv4 80.81.193.178: set Speed to 30000 (30G) (now 20000).
  3. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    Port speed differs1G30G
    • In the entry with IPv4 185.1.47.65: set Speed to 30000 (30G) (now 1000).
  4. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs20G30G
    • In the entry with IPv4 195.66.224.253: set Speed to 30000 (30G) (now 20000).

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