ixreport

UC Systems: PeeringDB fix list

AS39563 · peeringdb.com/net/24232

2 things to fix in UC Systems's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

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

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From 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. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.240.196 185.1.240.247185.1.240.196
    IPv6 address in PeeringDB, not in the export2001:7f8:12a::196 2001:7f8:12a::2472001:7f8:12a::196
    Port speed differs2 × 10G10G
    • The entry with IPv4 185.1.240.247, IPv6 2001:7f8:12a::247 isn't in the export: delete it if that connection is gone.

    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/39563/: 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.