bgpreport

Network · data from 2026-11-12

AS45294 PT. Wanriau Indoxp

Registry name: WANXP-AS-ID - PT. Wanriau Indoxp, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45294, 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.

160.236.1.0/24 No ROA None 661 98% 69
2404:6d00:5::/48 Valid Nonecovered by 2404:6d00::/34 634 100% 70
113.212.124.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
113.212.112.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
113.212.113.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
113.212.114.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
113.212.115.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
113.212.116.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
113.212.117.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
113.212.118.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
113.212.119.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
2404:6d00::/34 Valid Other IRR onlyNTTCOM 636 100% 69
2404:6d00:4000::/34 Valid Other IRR onlyNTTCOM 636 100% 69
2404:6d00:c000::/34 Valid Other IRR onlyNTTCOM 636 100% 69
2404:6d00:8000::/34 Valid Other IRR onlyNTTCOM 635 100% 70
45.64.252.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
45.64.253.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
45.64.254.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
45.64.255.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.19.208.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.19.211.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
113.212.120.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
113.212.123.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
113.212.125.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
113.212.126.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.19.209.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.19.210.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
113.212.121.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
113.212.122.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
113.212.127.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69

AS-SET

AS45294'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 199 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR13
  • Route object: not announced183
ChangePrefix or setDetailFull-table peers
ROA: none160.236.1.0/24No ROA covers it. Add a ROA for AS45294, maxLength 24.661 of 673
Route object: none160.236.1.0/24No route object for it. Add a route object with origin AS45294 in the RIR database for the space.661 of 673
Route object: none2404:6d00:5::/48No route object for it. A route object for 2404:6d00::/34 with origin AS45294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45294 in the RIR database for the space.634 of 636
Route object: RIR113.212.124.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR113.212.112.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.212.113.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.212.114.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.212.115.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.212.116.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.212.117.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.212.118.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.212.119.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2404:6d00::/34Route object only in NTTCOM. Add it in the RIR database for the space.636 of 636
Route object: RIR2404:6d00:4000::/34Route object only in NTTCOM. Add it in the RIR database for the space.636 of 636
Route object: RIR2404:6d00:c000::/34Route object only in NTTCOM. Add it in the RIR database for the space.636 of 636
Route object: RIR2404:6d00:8000::/34Route object only in NTTCOM. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

27.121.80.0/21NTTCOMNo ROA
27.121.80.0/22NTTCOMNo ROA
27.121.80.0/23NTTCOMNo ROA
27.121.82.0/23NTTCOMNo ROA
27.121.84.0/22NTTCOMNo ROA
27.121.84.0/23NTTCOMNo ROA
27.121.86.0/23NTTCOMNo ROA
45.64.252.0/22NTTCOM, RADBValid
45.64.252.0/23NTTCOM, RADBValid
45.64.254.0/23NTTCOM, RADBValid
103.19.208.0/22NTTCOM, RADBValid
103.19.208.0/23NTTCOM, RADBValid
103.19.210.0/23NTTCOM, RADBValid
103.54.2.0/23NTTCOMNo ROA
103.54.2.0/24NTTCOMNo ROA
103.54.3.0/24NTTCOMNo ROA
106.10.128.0/19RADBNo ROA
106.10.128.0/20RADBNo ROA
106.10.128.0/21RADBNo ROA
106.10.128.0/22RADBNo ROA
106.10.128.0/23RADBNo ROA
106.10.128.0/24RADBNo ROA
106.10.129.0/24RADBNo ROA
106.10.130.0/23RADBNo ROA
106.10.130.0/24RADBNo ROA
106.10.131.0/24RADBNo ROA
106.10.132.0/22RADBNo ROA
106.10.132.0/23RADBNo ROA
106.10.132.0/24RADBNo ROA
106.10.133.0/24RADBNo ROA
106.10.134.0/23RADBNo ROA
106.10.134.0/24RADBNo ROA
106.10.135.0/24RADBNo ROA
106.10.136.0/21RADBNo ROA
106.10.136.0/22RADBNo ROA
106.10.136.0/23RADBNo ROA
106.10.136.0/24RADBNo ROA
106.10.137.0/24RADBNo ROA
106.10.138.0/23RADBNo ROA
106.10.138.0/24RADBNo ROA
106.10.139.0/24RADBNo ROA
106.10.140.0/22RADBNo ROA
106.10.140.0/23RADBNo ROA
106.10.140.0/24RADBNo ROA
106.10.141.0/24RADBNo ROA
106.10.142.0/23RADBNo ROA
106.10.142.0/24RADBNo ROA
106.10.143.0/24RADBNo ROA
106.10.144.0/20RADBNo ROA
106.10.144.0/21RADBNo ROA
106.10.144.0/22RADBNo ROA
106.10.144.0/23RADBNo ROA
106.10.144.0/24RADBNo ROA
106.10.145.0/24RADBNo ROA
106.10.146.0/23RADBNo ROA
106.10.146.0/24RADBNo ROA
106.10.147.0/24RADBNo ROA
106.10.148.0/22RADBNo ROA
106.10.148.0/23RADBNo ROA
106.10.148.0/24RADBNo ROA
106.10.149.0/24RADBNo ROA
106.10.150.0/23RADBNo ROA
106.10.150.0/24RADBNo ROA
106.10.151.0/24RADBNo ROA
106.10.152.0/21RADBNo ROA
106.10.152.0/22RADBNo ROA
106.10.152.0/23RADBNo ROA
106.10.152.0/24RADBNo ROA
106.10.153.0/24RADBNo ROA
106.10.154.0/23RADBNo ROA
106.10.154.0/24RADBNo ROA
106.10.155.0/24RADBNo ROA
106.10.156.0/22RADBNo ROA
106.10.156.0/23RADBNo ROA
106.10.156.0/24RADBNo ROA
106.10.157.0/24RADBNo ROA
106.10.158.0/23RADBNo ROA
106.10.158.0/24RADBNo ROA
106.10.159.0/24RADBNo ROA
106.10.160.0/19RADBNo ROA
106.10.160.0/20RADBNo ROA
106.10.160.0/21RADBNo ROA
106.10.160.0/22RADBNo ROA
106.10.160.0/23RADBNo ROA
106.10.160.0/24RADBNo ROA
106.10.161.0/24RADBNo ROA
106.10.162.0/23RADBNo ROA
106.10.162.0/24RADBNo ROA
106.10.163.0/24RADBNo ROA
106.10.164.0/22RADBNo ROA
106.10.164.0/23RADBNo ROA
106.10.164.0/24RADBNo ROA
106.10.165.0/24RADBNo ROA
106.10.166.0/23RADBNo ROA
106.10.166.0/24RADBNo ROA
106.10.167.0/24RADBNo ROA
106.10.168.0/21RADBNo ROA
106.10.168.0/22RADBNo ROA
106.10.168.0/23RADBNo ROA
106.10.168.0/24RADBNo ROA
106.10.169.0/24RADBNo ROA
106.10.170.0/23RADBNo ROA
106.10.170.0/24RADBNo ROA
106.10.171.0/24RADBNo ROA
106.10.172.0/22RADBNo ROA
106.10.172.0/23RADBNo ROA
106.10.172.0/24RADBNo ROA
106.10.173.0/24RADBNo ROA
106.10.174.0/23RADBNo ROA
106.10.174.0/24RADBNo ROA
106.10.175.0/24RADBNo ROA
106.10.176.0/20RADBNo ROA
106.10.176.0/21RADBNo ROA
106.10.176.0/22RADBNo ROA
106.10.176.0/23RADBNo ROA
106.10.176.0/24RADBNo ROA
106.10.177.0/24RADBNo ROA
106.10.178.0/23RADBNo ROA
106.10.178.0/24RADBNo ROA
106.10.179.0/24RADBNo ROA
106.10.180.0/22RADBNo ROA
106.10.180.0/23RADBNo ROA
106.10.180.0/24RADBNo ROA
106.10.181.0/24RADBNo ROA
106.10.182.0/23RADBNo ROA
106.10.182.0/24RADBNo ROA
106.10.183.0/24RADBNo ROA
106.10.184.0/21RADBNo ROA
106.10.184.0/22RADBNo ROA
106.10.184.0/23RADBNo ROA
106.10.184.0/24RADBNo ROA
106.10.185.0/24RADBNo ROA
106.10.186.0/23RADBNo ROA
106.10.186.0/24RADBNo ROA
106.10.187.0/24RADBNo ROA
106.10.188.0/22RADBNo ROA
106.10.188.0/23RADBNo ROA
106.10.188.0/24RADBNo ROA
106.10.189.0/24RADBNo ROA
106.10.190.0/23RADBNo ROA
106.10.190.0/24RADBNo ROA
106.10.191.0/24RADBNo ROA
113.212.112.0/20NTTCOMValid
113.212.112.0/21APNIC, NTTCOM, RADBValid
113.212.112.0/22NTTCOM, RADBValid
113.212.112.0/23NTTCOM, RADBValid
113.212.114.0/23NTTCOM, RADBValid
113.212.116.0/22NTTCOM, RADBValid
113.212.116.0/23NTTCOM, RADBValid
113.212.118.0/23NTTCOM, RADBValid
113.212.120.0/21NTTCOM, RADBValid
113.212.120.0/22NTTCOM, RADBValid
113.212.120.0/23NTTCOM, RADBValid
113.212.122.0/23NTTCOM, RADBValid
113.212.124.0/22NTTCOM, RADBValid
113.212.124.0/23NTTCOM, RADBValid
113.212.126.0/23NTTCOM, RADBValid
122.128.16.0/21NTTCOMNo ROA
122.128.16.0/22NTTCOMNo ROA
122.128.16.0/23NTTCOMNo ROA
122.128.18.0/23NTTCOMNo ROA
122.128.20.0/22NTTCOMNo ROA
122.128.20.0/23NTTCOMNo ROA
122.128.22.0/23NTTCOMNo ROA
124.108.120.0/21RADBNo ROA
124.108.120.0/22RADBNo ROA
124.108.120.0/23RADBNo ROA
124.108.120.0/24RADBNo ROA
124.108.121.0/24RADBNo ROA
124.108.122.0/23RADBNo ROA
124.108.122.0/24RADBNo ROA
124.108.123.0/24RADBNo ROA
124.108.124.0/22RADBNo ROA
124.108.124.0/23RADBNo ROA
124.108.124.0/24RADBNo ROA
124.108.125.0/24RADBNo ROA
124.108.126.0/23RADBNo ROA
124.108.126.0/24RADBNo ROA
124.108.127.0/24RADBNo ROA
202.165.108.0/23RADBNo ROA
202.165.108.0/24RADBNo ROA
202.165.109.0/24RADBNo ROA
2404:6d00::/32NTTCOM, RADBValid

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.