bgpreport

Network · data from 2026-11-12

AS63528 BKNIX

Registry name: BKNIX-AS-AP - Bangkok Neutral Internet Exchange, TH · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
0No ROA 1 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS63528, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63528, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
203.159.71.250/32 Invalid: maxLength Nonecovered by 203.159.71.0/24 0 0%low visibility 1
203.159.66.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.159.70.0/23 Valid RIR databaseAPNIC, RADB 673 100% 67
203.159.66.0/23 Valid RIR databaseAPNIC, RADB 672 100% 67
2001:df5:b880::/48 Valid RIR databaseAPNIC, RADB 634 100% 69
2001:deb::/48 Valid RIR databaseAPNIC, RADB 633 100% 67
203.159.70.0/24 Valid RIR databaseAPNIC, RADB 40 6%low visibility 30
203.159.71.0/24 Valid RIR databaseAPNIC, RADB 40 6%low visibility 30

AS-SET

PeeringDB's irr_as_set for AS63528: APNIC::AS63528:AS-GOOGLE-VPP. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS63528 isn't in the set, or no route object for AS63528 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS63528 in itNot covered
APNIC::AS63528:AS-GOOGLE-VPP APNIC9 member sets in no database: AS-132280, AS-AKAMAI, AS-ANEXIA, AS-BBCONNECT, AS-CATONETWORKS-ASNS … 154236,374 Yes 1

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • AS-SET: missing member9
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength203.159.71.250/32ROA 203.159.68.0/22 AS63528 has maxLength 22; ROA 203.159.70.0/23 AS63528 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 203.159.71.250/32.0 of 673
Route object: none203.159.71.250/32No route object for it. A route object for 203.159.71.0/24 with origin AS63528 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63528 in the RIR database for the space.0 of 673
AS-SET: missing memberAPNIC::AS63528:AS-GOOGLE-VPPAS63528:AS-GOOGLE-VPP (APNIC) lists AS-132280; no IRR database read has it.
AS-SET: missing memberAPNIC::AS63528:AS-GOOGLE-VPPAS63528:AS-GOOGLE-VPP (APNIC) lists AS-AKAMAI; no IRR database read has it.
AS-SET: missing memberAPNIC::AS63528:AS-GOOGLE-VPPAS63528:AS-GOOGLE-VPP (APNIC) lists AS-ANEXIA; no IRR database read has it.
AS-SET: missing memberAPNIC::AS63528:AS-GOOGLE-VPPAS63528:AS-GOOGLE-VPP (APNIC) lists AS-BBCONNECT; no IRR database read has it.
AS-SET: missing memberAPNIC::AS63528:AS-GOOGLE-VPPAS63528:AS-GOOGLE-VPP (APNIC) lists AS-CATONETWORKS-ASNS; no IRR database read has it.
AS-SET: missing memberAPNIC::AS63528:AS-GOOGLE-VPPAS63528:AS-GOOGLE-VPP (APNIC) lists AS-ITSC; no IRR database read has it.
AS-SET: missing memberAPNIC::AS63528:AS-GOOGLE-VPPAS63528:AS-GOOGLE-VPP (APNIC) lists AS-NETSKOPE; no IRR database read has it.
AS-SET: missing memberAPNIC::AS63528:AS-GOOGLE-VPPAS63528:AS-GOOGLE-VPP (APNIC) lists AS-TRUEIDC-TH; no IRR database read has it.
AS-SET: missing memberAPNIC::AS63528:AS-GOOGLE-VPPAS63528:AS-GOOGLE-VPP (APNIC) lists AS-UIH; no IRR database read has it.

Route objects not announced

Route objects with origin AS63528 whose prefix no peer sees AS63528 announce. Many are kept on purpose (backup routes, space announced only in some places).

203.159.67.0/24APNIC, RADBValid
203.159.68.0/22APNICValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.