Exchanges · data from 2026-11-12
BKNIX Chiang Mai (Thailand) BKNIX Chiang Mai
Chiang Mai, TH · members from IX Report (2026-11-12)
Route servers: RPKI + IRR filtering
For each member on the route servers: of the routes it originates, how many a route server would leave out if it dropped RPKI-invalid routes and filtered on the IRR the way IXP route servers commonly build their prefix lists: the member's AS-SETs from PeeringDB (with none, its own AS number), expanded as bgpq4 does against whois.radb.net, with more-specifics of a route object accepted down to /24 and /48 (bgpq4 -A -R 24 / -R 48). 3 routes are RPKI invalid and 10 fail the IRR filter. Only each member's own routes are counted: the collectors show a route's origin, not which network it came through, so customers' routes aren't in these numbers. Route objects only in LEVEL3 or IDNIC (no public dump) count as missing.
| AS42PCH AS42 | RADB::AS-PCH | 418 | 0 | 6 | 6 1% |
| AS59238ByteArk | AS-INOX | 22 | 2 | 2 | 2 9% |
| AS4621UniNet Thailand | RADB::AS-UNINET | 82 | 0 | 1 | 1 1% |
| AS63528BKNIX | APNIC::AS63528:AS-GOOGLE-VPP | 8 | 1 | 1 | 1 12% |
3 other route-server members would have every route they originate accepted; 1 originate no routes the collectors see.
Members
Every member on IX Report's lists for BKNIX Chiang Mai (Thailand), with the routes it originates. Also as members.csv.
| AS42PCH AS42 | 418210 v4 · 208 v6 | 99% | 0 |
| AS4621UniNet Thailand | 8279 v4 · 3 v6 | 83% | 0 |
| AS59238ByteArk | 2210 v4 · 12 v6 | 91% | 2 |
| AS17479Chiang Mai University | 1817 v4 · 1 v6 | 100% | 0 |
| AS63528BKNIX | 86 v4 · 2 v6 | 88% | 1 |
| AS3856PCH AS3856 | 21 v4 · 1 v6 | 100% | 0 |
| AS141362Thai Name Server Co. | 21 v4 · 1 v6 | 100% | 0 |
| AS63529BKNIX Route Servers | none seen |