CommunityDNS Ltd: PeeringDB fix list

AS42909 · peeringdb.com/net/7871

PeeringDB

9 things to fix in CommunityDNS Ltd's PeeringDB record, from what its exchanges publish: 4 to add, 4 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on CommunityDNS Ltd'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 (4)

On the exchange's own member list, but not in CommunityDNS Ltd's PeeringDB record. Add one entry per connection with these values.

  1. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716From its website members list

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

  2. Brazil IX.br (PTT.br) Curitiba Curitiba, Brazil · PeeringDB 174From 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.

  3. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488From its IX-F export
    IPv4196.216.148.29
    IPv6–
    Speed1000 Mbps (1G)
    RS peerYes
  4. Russia ULN-IX Ulyanovsk, Russia · PeeringDB 340From its IX-F export
    IPv4185.1.19.11
    IPv62001:7f8:7d::a79d:1
    SpeedNot published
    RS peerNot published

Correct these entries (4)

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. Thailand BKNIX (Thailand) Bangkok, Thailand · PeeringDB 1025
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 203.159.68.8: set Speed to 1000 (1G) (now 10000).

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

  2. Kazakhstan KazNIX Semey, Kazakhstan · PeeringDB 2497
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 185.79.213.68: set Speed to 1000 (1G) (now 10000).

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

  3. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 188.93.170.77: set Speed to 1000 (1G) (now 10000).

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

  4. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 103.16.102.68: set Speed to 1000 (1G) (now 10000).

Check these entries (1)

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

  1. Armenia ArmIX Yerevan, Armenia · PeeringDB 851Not on its website members list
    IPv491.218.7.73
    IPv62001:7f8:94::cd
    Speed1000 Mbps (1G)

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

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