ixreport

Bezeq: PeeringDB fix list

AS6810 · peeringdb.com/net/29620

PeeringDB

2 things to fix in Bezeq's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Bezeq's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Bezeq's PeeringDB record. Add one entry per connection with these values.

  1. Germany MegaIX Frankfurt Frankfurt, Germany · PeeringDB 676From its IX-F export
    IPv462.69.146.57
    IPv62001:7f8:8:20:0:1a9a:0:1
    SpeedNot published
    RS peerNo

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Bezeq has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. France DE-CIX Marseille Marseille, France · PeeringDB 1149Not on its IX-F export or website members list
    IPv4185.1.47.17
    IPv62001:7f8:36::1a9a:0:1
    Speed100000 Mbps (100G)

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