bgpreport

Network · data from 2026-11-12

AS55679 Hyperindo Media Perkasa

Registry name: HYPERMEDIA-AS-ID - PT Hyperindo Media Perkasa, ID · PeeringDB

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

Announced routes

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

202.92.200.0/24 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67
202.92.201.0/24 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67
202.92.202.0/24 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67
202.92.203.0/24 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67
202.92.206.0/24 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67
202.92.207.0/24 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67
202.92.205.0/24 No ROA Other IRR onlyNTTCOM, RADB 3 0%low visibility 4

AS-SET

AS55679'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 32 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none202.92.200.0/24No ROA covers it. Add a ROA for AS55679, maxLength 24.669 of 673
Route object: RIR202.92.200.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
ROA: none202.92.201.0/24No ROA covers it. Add a ROA for AS55679, maxLength 24.669 of 673
Route object: RIR202.92.201.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
ROA: none202.92.202.0/24No ROA covers it. Add a ROA for AS55679, maxLength 24.669 of 673
Route object: RIR202.92.202.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
ROA: none202.92.203.0/24No ROA covers it. Add a ROA for AS55679, maxLength 24.669 of 673
Route object: RIR202.92.203.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
ROA: none202.92.206.0/24No ROA covers it. Add a ROA for AS55679, maxLength 24.669 of 673
Route object: RIR202.92.206.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
ROA: none202.92.207.0/24No ROA covers it. Add a ROA for AS55679, maxLength 24.669 of 673
Route object: RIR202.92.207.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
ROA: none202.92.205.0/24No ROA covers it. Add a ROA for AS55679, maxLength 24.3 of 673
Route object: RIR202.92.205.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

43.240.148.0/22RADBNo ROA
43.240.148.0/23NTTCOM, RADBNo ROA
43.240.150.0/23NTTCOM, RADBNo ROA
202.92.192.0/20NTTCOMNo ROA
202.92.192.0/22NTTCOMNo ROA
202.92.192.0/23NTTCOMNo ROA
202.92.194.0/23NTTCOMNo ROA
202.92.196.0/22NTTCOMNo ROA
202.92.196.0/23NTTCOMNo ROA
202.92.198.0/23NTTCOMNo ROA
202.92.200.0/21NTTCOM, RADBNo ROA
202.92.200.0/22NTTCOMNo ROA
202.92.200.0/23NTTCOMNo ROA
202.92.202.0/23NTTCOMNo ROA
202.92.204.0/22NTTCOMNo ROA
202.92.204.0/23NTTCOMNo ROA
202.92.206.0/23NTTCOMNo ROA
2403:8cc0::/32RADBValid

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.