ixreport

BKNIX Route Servers

AS63529 · BKNIX RS

BKNIX

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Route ServerType
OpenPeering policy
2Using the route servers
2To fix in PeeringDB
7Facilities in PeeringDB

Tools: Where can I peer with BKNIX Route Servers? · Where should BKNIX Route Servers peer next? · Compare BKNIX Route Servers with another network

This network elsewhere: the registry history of AS63528-AS63529, the block AS63529 is in, on RIR Tracker

PeeringDB fix list Printable page · CSV

2 things to fix in BKNIX Route Servers's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on BKNIX Route Servers's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (2)

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
    IPv4 address missing from PeeringDB203.159.68.68 203.159.68.69203.159.68.67 203.159.68.68 203.159.68.69 203.159.68.70 203.159.69.0 203.159.69.1
    IPv6 address missing from PeeringDB2001:df5:b881::68 2001:df5:b881::692001:df5:b881::67 2001:df5:b881::68 2001:df5:b881::69 2001:df5:b881::70 2001:df5:b881::691 2001:df5:b881::dead
    Port speed differs2 × 10G200G + 4 × 20G
    • In the entry with IPv4 203.159.68.68: set Speed to 20000 (20G) (now 10000).
    • In the entry with IPv4 203.159.68.69: set Speed to 200000 (200G) (now 10000).
    • Add an entry: IPv4 203.159.69.0, IPv6 2001:df5:b881::dead, speed 20000 (20G), RS peer no.
    • Add an entry: IPv4 203.159.69.1, IPv6 2001:df5:b881::691, speed 20000 (20G), RS peer no.
    • Add an entry: IPv4 203.159.68.67, IPv6 2001:df5:b881::67, speed 20000 (20G), RS peer no.
    • Add an entry: IPv4 203.159.68.70, IPv6 2001:df5:b881::70, speed 20000 (20G), RS peer no.

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

  2. ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 1G
    • In the entry with IPv4 203.159.67.6: set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 203.159.67.7: 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.

Exchanges over time

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

Map

Where BKNIX Route Servers'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 40G across 2 exchanges.

Thailand BKNIX (Thailand) Bangkok, Thailand 203.159.68.68
203.159.68.69
2001:df5:b881::68
2001:df5:b881::69
2 × 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Thailand BKNIX Chiang Mai (Thailand) Chiang Mai, Thailand 203.159.67.6
203.159.67.7
2001:df5:b881:1::6
2001:df5:b881:1::7
2 × 10G Yes Both Speed differs

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

These exchanges have a switch in a facility where BKNIX Route Servers lists itself in PeeringDB, but don't have BKNIX Route Servers 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 (7)

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