ixreport

MekongNet: PeeringDB fix list

AS38235 · peeringdb.com/net/4063

PeeringDB

3 things to fix in MekongNet's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check, 1 at exchanges that look shut down. As of 2026-10-08 18:53 UTC.

Make the changes on MekongNet'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 (1)

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

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From 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.

Check these entries (1)

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

  1. Thailand THAILAND IX (TH-IX) Bangkok, Thailand · PeeringDB 225Not on its website members list
    IPv461.19.60.141
    IPv62001:c38:8000::3:8235:2
    Speed10000 Mbps (10G)

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

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. Cambodia MekongIXghost Phnom Penh, Cambodia · PeeringDB 2802

    Only one outside network

    IPv4202.57.208.33
    IPv62001:deb:4000::a1
    Speed100000 Mbps (100G)

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