ixreport

ARTRUBY: PeeringDB fix list

AS212628 · peeringdb.com/net/39001

PeeringDB

4 things to fix in ARTRUBY's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

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

  1. Hong Kong Hong Kong Global Internet Exchange Hong Kong, Hong Kong · PeeringDB 4625From its IX-F export and website members list

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

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Canada TorIX Toronto, Canada · PeeringDB 24From its website members list
    IPv4206.108.34.98
    IPv62001:504:1a::34:98
    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 DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDB2001:504:61:0:3:3e94:0:12001:504:61:0:3:3e94:0:1 2001:504:61:0:3:3e94:0:2
    • In the entry with IPv4 206.53.202.206: set IPv6 to 2001:504:61:0:3:3e94:0:2 (now empty).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If ARTRUBY has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126Not on its website members list
    IPv4101.203.90.172
    IPv62001:de8:c::21:2628:1
    Speed100000 Mbps (100G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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