bgpreport

Network · data from 2026-11-12

AS46058 LINKS-AS-ID - PT. Triwahana Gemasakti

Registry name: LINKS-AS-ID - PT. Triwahana Gemasakti, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46058, 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.52.58.103/32 Invalid: maxLength Nonecovered by 202.52.58.0/24 2 0%low visibility 4
202.52.58.146/32 Invalid: maxLength Nonecovered by 202.52.58.0/24 2 0%low visibility 4
202.52.58.0/23 Valid Other IRR onlyRADB 673 100% 69
202.52.58.0/24 Valid Other IRR onlyRADB 673 100% 69
202.52.59.0/24 Valid Other IRR onlyRADB 673 100% 69

AS-SET

AS46058 isn't in PeeringDB, where networks name their 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 7 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: maxLength202.52.58.103/32ROA 202.52.58.0/23 AS46058 has maxLength 23; ROA 202.52.58.0/24 AS46058 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 202.52.58.103/32.2 of 673
Route object: none202.52.58.103/32No route object for it. A route object for 202.52.58.0/24 with origin AS46058 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS46058 in the RIR database for the space.2 of 673
ROA: maxLength202.52.58.146/32ROA 202.52.58.0/23 AS46058 has maxLength 23; ROA 202.52.58.0/24 AS46058 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 202.52.58.146/32.2 of 673
Route object: none202.52.58.146/32No route object for it. A route object for 202.52.58.0/24 with origin AS46058 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS46058 in the RIR database for the space.2 of 673
Route object: RIR202.52.58.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.52.58.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.52.59.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS46058 is announced.

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.