ixreport

Exascale: PeeringDB fix list

AS61049 · peeringdb.com/net/6536

PeeringDB

2 things to fix in Exascale's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 21:56 UTC.

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

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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 Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    Port speed differs20G + 10G2 × 10G
    • In the entry with IPv4 195.66.244.58: set Speed to 10000 (10G) (now 20000).

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