IPTELECOM GLOBAL: PeeringDB fix list

AS63916 · peeringdb.com/net/9852

PeeringDB

3 things to fix in IPTELECOM GLOBAL's PeeringDB record, from what its exchanges publish: 2 to add, 1 to check. As of 2026-10-08 21:35 UTC.

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

  1. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4103.162.254.40
    IPv62001:df6:480::f9ac:0:1
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4103.162.254.41
    IPv62001:df6:480::f9ac:0:2
    Speed10000 Mbps (10G)
    RS peerYes
  2. Hong Kong HKIX Hong Kong, Hong Kong · PeeringDB 42From its IX-F export

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

Check these entries (1)

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

  1. United States Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142Not on its website members list
    IPv4206.72.211.170
    IPv62001:504:13::211:170
    Speed10000 Mbps (10G)

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

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