UPP Microcomponent: PeeringDB fix list
AS42394 · peeringdb.com/net/26569
3 things to fix in UPP Microcomponent's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on UPP Microcomponent'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 (2)
On the exchange's own member list, but not in UPP Microcomponent's PeeringDB record. Add one entry per connection with these values.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members listIPv4 – IPv6 2001:7f8:d0::a59a:1 Speed Not published RS peer Yes -
IPv4 – IPv6 2a0e:46c4:102::423:94:1 Speed Not published RS peer Not published
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.
-
Problem PeeringDB has The export has Port speed differs 3 × 2G 2 × 1G - In the entry with IPv6 2602:fed2:fff:ffff::94: set Speed to 1000 (1G) (now 2000).
- In the entry with IPv4 206.81.104.54: set Speed to 1000 (1G) (now 2000).
- The entry with IPv4 206.81.104.94, IPv6 2602:fed2:fff:ffff::54 isn't in the export: delete it if that connection is gone.
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/42394/: 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.