ixreport

Bezeq International: PeeringDB fix list

AS8551 · peeringdb.com/net/1014

PeeringDB

4 things to fix in Bezeq International's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Bezeq International'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. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 100G
    • In the entry with IPv4 185.1.170.52: set Speed to 100000 (100G) (now 10000).
    • In the entry with IPv4 185.1.170.58: set Speed to 100000 (100G) (now 10000).
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 100G
    • In the entry with IPv4 185.1.210.73: set Speed to 100000 (100G) (now 10000).
    • In the entry with IPv4 185.1.210.75: set Speed to 100000 (100G) (now 10000).
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 100G
    • In the entry with IPv4 185.1.208.62: set Speed to 100000 (100G) (now 10000).
    • In the entry with IPv4 185.1.208.67: set Speed to 100000 (100G) (now 10000).
  4. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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