ixreport

UPP Microcomponent

AS42394

UPP Microcomponent LLC

3Exchanges, of which 2 VIX
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
2Using the route servers
3To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with UPP Microcomponent? · Where should UPP Microcomponent peer next? · Compare UPP Microcomponent with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in UPP Microcomponent's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-11-19 12:40 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.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::a59a:1
    SpeedNot published
    RS peerYes
  2. Egypt PyramIX Cairo, Egypt · PeeringDB 3302From its website members list
    IPv4–
    IPv62a0e:46c4:102::423:94:1
    SpeedNot published
    RS peerNot 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.

  1. United States EVIX Fremont, United States · PeeringDB 2274
    ProblemPeeringDB hasThe export has
    Port speed differs3 × 2G2 × 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.

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where UPP Microcomponent's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 6G, at the 1 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::a59a:1 Yes Not in PeeringDB
United States EVIXVIX Fremont, United States 206.81.104.54
206.81.104.94
2602:fed2:fff:ffff::54
2602:fed2:fff:ffff::94
3 × 2G 2 routes Both Speed differs
Egypt PyramIXVIX Cairo, Egypt 2a0e:46c4:102::423:94:1 Website list only

UPP Microcomponent lists no facilities in PeeringDB.