bgpreport

Network · data from 2026-11-12

AS45302 DES Teknologi Informasi

Registry name: DESNET-AS-ID - PT DES Teknologi Informasi, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45302, 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.
2403:9100:1::/48 Valid Nonecovered by 2403:9100::/40 635 100% 67
2403:9100:200::/40 Valid Nonecovered by 2403:9100::/32 635 100% 67
103.30.180.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
112.78.40.0/21 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
112.78.42.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
157.119.220.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
112.78.45.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
157.119.221.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
157.119.223.0/24 Valid Other IRR onlyNTTCOM 672 100% 68
157.119.220.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 68
2403:9100::/32 Valid Other IRR onlyRADB 636 100% 67
2403:9100::/40 Valid Other IRR onlyRADB 635 100% 67
157.119.222.0/24 Valid Other IRR onlyNTTCOM, RADB 37 5%low visibility 28
157.119.222.0/23 Valid Other IRR onlyNTTCOM 2 0%low visibility 2
103.30.181.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 70
103.30.183.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
112.78.41.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
112.78.44.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
112.78.43.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
112.78.47.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.30.180.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
103.30.182.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
112.78.40.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
112.78.46.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 623 93% 67

AS-SET

AS45302'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 30 are in fix.csv.

  • Route object: none2
  • Route object: RIR12
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
Route object: none2403:9100:1::/48No route object for it. A route object for 2403:9100::/40 with origin AS45302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45302 in the RIR database for the space.635 of 636
Route object: none2403:9100:200::/40No route object for it. A route object for 2403:9100::/32 with origin AS45302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45302 in the RIR database for the space.635 of 636
Route object: RIR103.30.180.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR112.78.40.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR112.78.42.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.119.220.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR112.78.45.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR157.119.221.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR157.119.223.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR157.119.220.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2403:9100::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2403:9100::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR157.119.222.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.37 of 673
Route object: RIR157.119.222.0/23Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

103.28.220.0/22NTTCOMNo ROA
103.28.220.0/23NTTCOMNo ROA
103.28.220.0/24NTTCOMNo ROA
103.28.221.0/24NTTCOMNo ROA
103.28.222.0/23NTTCOMNo ROA
103.28.222.0/24NTTCOMNo ROA
103.28.223.0/24NTTCOMNo ROA
103.30.180.0/23NTTCOM, RADBValid
103.30.182.0/23NTTCOM, RADBValid
112.78.40.0/22NTTCOM, RADBValid
112.78.40.0/23APNIC, NTTCOM, RADBValid
112.78.42.0/23NTTCOM, RADBValid
112.78.44.0/22NTTCOM, RADBValid
112.78.44.0/23NTTCOM, RADBValid
112.78.46.0/23NTTCOM, RADBValid
157.119.220.0/23NTTCOM, 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.