bgpreport

Network · data from 2026-11-12

AS132300 NIPA Cloud Space

Registry name: NIPA-AS-TH - NIPA TECHNOLOGY CO., LTD, TH · PeeringDB

31IPv4 routes 96.8% RPKI valid · 100.0% with a route object
4IPv6 routes 25.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS132300, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132300, 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.
2400:7900:7226::/48 No ROA None 5 1%low visibility 4
183.90.168.0/21 No ROA Other IRR onlyRADB 673 100% 68
2406:7900:9000::/48 No ROA Other IRR onlyRADB 631 99% 70
2406:7900:9001::/48 No ROA Other IRR onlyRADB 631 99% 70
103.212.36.0/24 Valid Other IRR onlyRADB 673 100% 68
103.212.37.0/24 Valid Other IRR onlyRADB 673 100% 68
103.212.39.0/24 Valid Other IRR onlyRADB 673 100% 68
202.94.169.0/24 Valid Other IRR onlyRADB 673 100% 68
103.74.253.0/24 Valid Other IRR onlyRADB 672 100% 68
103.212.36.0/22 Valid Other IRR onlyRADB 672 100% 68
103.212.38.0/24 Valid Other IRR onlyRADB 672 100% 68
139.5.144.0/24 Valid Other IRR onlyRADB 672 100% 68
202.94.168.0/22 Valid Other IRR onlyRADB 672 100% 68
202.94.168.0/24 Valid Other IRR onlyRADB 672 100% 68
202.94.170.0/24 Valid Other IRR onlyRADB 672 100% 68
202.94.171.0/24 Valid Other IRR onlyRADB 672 100% 68
45.121.60.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
45.121.62.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
45.121.63.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.29.189.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.29.191.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
183.90.168.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
183.90.169.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
183.90.170.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
183.90.171.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
183.90.175.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.129.205.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.129.206.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.129.207.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.29.188.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
103.29.190.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
183.90.172.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
183.90.173.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
183.90.174.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
2406:7900:7226::/48 Valid RIR databaseAPNIC, RADB 636 100% 69

AS-SET

AS132300's PeeringDB record names no 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 33 are in fix.csv.

  • ROA: none4
  • Route object: none1
  • Route object: RIR15
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none2400:7900:7226::/48No ROA covers it. Add a ROA for AS132300, maxLength 48.5 of 636
Route object: none2400:7900:7226::/48No route object for it. Add a route object with origin AS132300 in the RIR database for the space.5 of 636
ROA: none183.90.168.0/21No ROA covers it. Add a ROA for AS132300, maxLength 21.673 of 673
Route object: RIR183.90.168.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2406:7900:9000::/48No ROA covers it. Add a ROA for AS132300, maxLength 48.631 of 636
Route object: RIR2406:7900:9000::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2406:7900:9001::/48No ROA covers it. Add a ROA for AS132300, maxLength 48.631 of 636
Route object: RIR2406:7900:9001::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR103.212.36.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.212.37.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.212.39.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.94.169.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.74.253.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.212.36.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.212.38.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.5.144.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.94.168.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.94.168.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.94.170.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.94.171.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 AS132300 whose prefix no peer sees AS132300 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.121.61.0/24APNIC, RADBValid
103.29.188.0/22RADBNo ROA
103.74.252.0/22RADBValid
103.74.252.0/24RADBValid
103.74.254.0/24RADBValid
103.74.255.0/24RADBValid
139.5.144.0/22RADBNo ROA
139.5.145.0/24RADBValid
139.5.146.0/24RADBValid
139.5.147.0/24RADBValid
183.90.168.0/22APNICValid
183.90.172.0/23APNICValid
2406:7900:8999::/48RADBNo 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.