bgpreport

Network · data from 2026-11-12

AS38506 PT. Pika Media Komunika

Registry name: PIKANET-AS-ID - PT Pika Media Komunika, ID · PeeringDB

15IPv4 routes 100.0% RPKI valid · 100.0% with a route object
18IPv6 routes 100.0% RPKI valid · 11.1% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 16 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
23Route objects not announced registered with origin AS38506, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38506, 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.
2406:9300::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:1::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:2::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:3::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:4::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:5::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:6::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:7::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:8::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:9::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:a::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:b::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:c::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:d::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:e::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
2406:9300:f::/48 Valid Nonecovered by 2406:9300::/32 635 100% 70
117.103.168.0/23 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.172.0/23 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
117.103.174.0/23 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
2406:9300:ffff::/48 Valid Other IRR onlyRADB 635 100% 70
2406:9300::/32 Valid Other IRR onlyRADB 634 100% 70
117.103.168.0/21 Valid Other IRR onlyNTTCOM, RADB 38 6%low visibility 30
117.103.168.0/22 Valid Other IRR onlyNTTCOM, RADB 38 6%low visibility 30
117.103.170.0/23 Valid Other IRR onlyNTTCOM, RADB 38 6%low visibility 30
117.103.172.0/22 Valid Other IRR onlyNTTCOM, RADB 38 6%low visibility 30
117.103.169.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
117.103.170.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
117.103.172.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
117.103.173.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
117.103.174.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
117.103.175.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
117.103.171.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 68
117.103.168.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 35 5%low visibility 29

AS-SET

AS38506'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 48 are in fix.csv.

  • Route object: none16
  • Route object: RIR9
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
Route object: none2406:9300::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:1::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:2::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:3::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:4::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:5::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:6::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:7::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:8::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:9::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:a::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:b::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:c::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:d::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:e::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: none2406:9300:f::/48No route object for it. A route object for 2406:9300::/32 with origin AS38506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38506 in the RIR database for the space.635 of 636
Route object: RIR117.103.168.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.172.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.174.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2406:9300:ffff::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2406:9300::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR117.103.168.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.38 of 673
Route object: RIR117.103.168.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.38 of 673
Route object: RIR117.103.170.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.38 of 673
Route object: RIR117.103.172.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.38 of 673

Route objects not announced

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

58.145.170.0/24APNICInvalid: origin
103.5.48.0/23NTTCOMNo ROA
103.5.48.0/24NTTCOMNo ROA
103.5.49.0/24NTTCOMNo ROA
103.24.56.0/22NTTCOMNo ROA
103.24.56.0/23NTTCOMNo ROA
103.24.58.0/23NTTCOMNo ROA
103.195.18.0/23NTTCOMNo ROA
110.76.144.0/21NTTCOM, RADBNo ROA
110.76.144.0/22NTTCOM, RADBNo ROA
110.76.144.0/24APNICInvalid: origin
110.76.145.0/24APNICInvalid: origin
110.76.146.0/24APNICInvalid: origin
110.76.147.0/24APNICInvalid: origin
110.76.148.0/22NTTCOM, RADBNo ROA
110.76.148.0/24APNICInvalid: origin
110.76.149.0/24APNICInvalid: origin
110.76.150.0/24APNICInvalid: origin
110.76.151.0/24APNICInvalid: origin
111.92.162.0/23NTTCOM, RADBNo ROA
111.92.162.0/24NTTCOM, RADBValid
111.92.163.0/24NTTCOMNo ROA
2403:b200:a99c::/48RADBValid

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.