bgpreport

Network · data from 2026-11-12

AS7630 KASIKORNBANK-AS-AP - KASIKORNBANK PUBLIC COMPANY LIMITED

Registry name: KASIKORNBANK-AS-AP - KASIKORNBANK PUBLIC COMPANY LIMITED, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7630, 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.148.162.0/24 Invalid: origin Other origin only 20 3%low visibility 16
203.148.163.0/24 No ROA Other origin only 672 100% 67
103.151.51.0/24 No ROA Other IRR onlyRADB 672 100% 66
49.231.212.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 66
49.231.240.0/24 Valid Other IRR onlyRADB 672 100% 66
58.137.161.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
110.170.223.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
203.146.18.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
203.146.224.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
203.146.225.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.1.22.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.1.2.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
210.86.192.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.151.50.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
2406:1440:1101::/48 Valid RIR databaseAPNIC, RADB 631 99% 70

AS-SET

AS7630 isn't in PeeringDB, where networks name their AS-SET.

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 12 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin203.148.162.0/24ROAs covering it name AS4776, not AS7630. If AS7630 should announce it, add a ROA for AS7630.20 of 673
Route object: none203.148.162.0/24Route objects for it name AS4750, AS4776. Add a route object with origin AS7630 in the RIR database for the space.20 of 673
ROA: none203.148.163.0/24No ROA covers it. Add a ROA for AS7630, maxLength 24.672 of 673
Route object: none203.148.163.0/24Route objects for it name AS4776, AS38082. Add a route object with origin AS7630 in the RIR database for the space.672 of 673
ROA: none103.151.51.0/24No ROA covers it. Add a ROA for AS7630, maxLength 24.672 of 673
Route object: RIR103.151.51.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR49.231.212.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR49.231.240.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.151.50.0/23RADBNo ROA
203.146.224.0/23NTTCOM, RADBNo ROA
203.148.170.0/24RADBNo ROA
2406:1440::/32RADBNo ROA

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.