ARIX: operator report

Fremont, Portland, Flagstaff, United States · PeeringDB 3069 · ixreport.com/ix/3069/report/

Download CSV

Members of ARIX that PeeringDB has wrong, from its IX-F export (22 networks, read 2026-10-08 20:54 UTC) and its website members list (22 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 3 networks to follow up.

Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.

On your lists, missing from PeeringDB (2)

These networks could add ARIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS7480 Tsung-Yi Yu PeeringDBIX-F and website 44.190.42.14
2602:801:30ff::14
1G
No public contact
AS60564 Azignshop PeeringDBIX-F and website 44.190.42.6
2602:801:30ff::6
10G
No public contact

Addresses or port speeds that differ (1)

PeeringDB against your IX-F export, for the 20 networks in both. Either the network's PeeringDB record or the export is out of date.

NetworkProblemPeeringDB hasYour export hasContact
AS6556 Airgapped PeeringDB Port speed differs1G10G No public contact

In PeeringDB, not on your lists (0)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

None.