ixreport

MekongNet

AS38235 · Angkor Data Communication Group (ADC)

MekongNet IXP

6Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
5Using the route servers
1To fix in PeeringDB
5Facilities in PeeringDB

Tools: Where can I peer with MekongNet? · Where should MekongNet peer next? · Compare MekongNet with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in MekongNet's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 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.

Exchanges over time

0246810Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20266
Oct 19, 20269
Oct 18, 20269
Oct 17, 20269
Oct 16, 20269
Oct 15, 20269
Oct 14, 20269
Oct 13, 20269
Oct 12, 20269
Oct 11, 20269
Oct 10, 20269
Oct 9, 20269
Oct 8, 20269
Oct 7, 20268
Oct 6, 20268
Oct 5, 20268
Oct 4, 20268
Oct 3, 20268

Map

Where MekongNet's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 410G, at the 5 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Japan BBIX Tokyo Tokyo, Japan Not in PeeringDB
Cambodia CNX Phnom Penh, Cambodia 103.7.144.11 2001:de8:1d::11 100G 250 routes Both
Hong Kong Equinix Hong Kong Hong Kong, Hong Kong 36.255.56.211 2001:de8:7::3:8235:1 100G Yes PeeringDB
Singapore Equinix Singapore Singapore, Singapore 27.111.230.202 2001:de8:4::3:8235:1 100G Yes PeeringDB
Hong Kong HKIX Hong Kong, Hong Kong 123.255.90.134 2001:7fa:0:1::ca28:a086 100G Yes Both
Singapore SGIX Singapore, Singapore 103.16.102.227 2001:de8:12:100::227 10G Yes Both

Exchanges in its buildings that it isn't on (21)

These exchanges have a switch in a facility where MekongNet lists itself in PeeringDB, but don't have MekongNet as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (5)

The buildings MekongNet lists in PeeringDB, and how many of the exchanges in each it's on.

Singapore Equinix SG1 - SingaporeSingapore 2 of 11
Thailand Telehouse – BangkokBangkok 0 of 10
Hong Kong MEGA-i (iAdvantage Hong Kong)Hong Kong 1 of 4
Cambodia MekongNetPhnom Penh 1 of 1
Cambodia MekongNet DCPhnom Penh No exchange

Recent changes Search them

  • Oct 20, 2026 [PDB] AS38235 MekongNet now in PeeringDB at HKIX
  • Oct 20, 2026 [PDB] AS38235 MekongNet left THAILAND IX (TH-IX)
  • Oct 20, 2026 [PDB] AS38235 MekongNet left BBIX Thailand
  • Oct 20, 2026 [PDB] AS38235 MekongNet left MekongIX
  • Oct 12, 2026 [IXF] AS38235 MekongNet now on HKIX's IX-F list