ixreport

Alex Delporte: PeeringDB fix list

AS213045 · peeringdb.com/net/23716

PeeringDB

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

Make the changes on Alex Delporte'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 Alex Delporte's PeeringDB record. Add one entry per connection with these values.

  1. Egypt PyramIX Cairo, Egypt · PeeringDB 3302From its IX-F export and website members list
    IPv4–
    IPv62a0e:46c4:102::213:45:1
    Speed100 Mbps (100M)
    RS peerYes

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

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 EVIX Fremont, United States · PeeringDB 2274
    ProblemPeeringDB hasThe export has
    Port speed differs100M1G
    • In the entry with IPv6 2602:fed2:fff:ffff:6::34: set Speed to 1000 (1G) (now 100).

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

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