ixreport

DTAC NIX: PeeringDB fix list

AS133543 · peeringdb.com/net/18656

PeeringDB

2 things to fix in DTAC NIX's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on DTAC NIX'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 DTAC NIX'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.

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. Thailand BKNIX (Thailand) Bangkok, Thailand · PeeringDB 1025
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G + 10G
    • In the entry with IPv4 203.159.68.104: set Speed to 10000 (10G) (now 100000).

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

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