Exabytes Network Malaysia: PeeringDB fix list

AS46015 · peeringdb.com/net/4254

PeeringDB

4 things to fix in Exabytes Network Malaysia's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Exabytes Network Malaysia'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 (3)

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

  1. Malaysia DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia · PeeringDB 3473From its IX-F export

    2 connections, so 2 entries:

    IPv4103.119.234.1
    IPv62403:4ac0:1::b3bf:0:1
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4103.119.234.36
    IPv62403:4ac0:1::b3bf:0:2
    Speed1000 Mbps (1G)
    RS peerYes
  2. Malaysia DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia · PeeringDB 3474From its IX-F export
    IPv4103.119.232.10
    IPv62403:4ac0::b3bf:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  3. Malaysia Penang IX Penang, Malaysia · PeeringDB 4269From its IX-F export
    IPv4103.10.57.4
    IPv62001:deb:c001::b3bf:0:1
    Speed1000 Mbps (1G)
    RS peerYes

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. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:df6:480::812001:df6:480::b3bf:0:1 2001:df6:480::b3bf:0:2
    IPv4 address missing from PeeringDB103.162.254.81103.162.254.81 103.162.254.110
    Port speed differs1G10G + 1G
    • In the entry with IPv4 103.162.254.81: set IPv6 to 2001:df6:480::b3bf:0:1 (now 2001:df6:480::81); set Speed to 10000 (10G) (now 1000).
    • Add an entry: IPv4 103.162.254.110, IPv6 2001:df6:480::b3bf:0:2, speed 1000 (1G), RS peer yes.

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