bgpreport

Network · data from 2026-11-12

AS149672 PT Aktech Digital Solutions

Registry name: IDNIC-FASTLINK-AS-ID - PT Aktech Digital Solutions, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149672, 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.
2001:df2:5e40::/48 No ROA Other IRR onlyRADB 636 100% 68
154.58.230.0/24 No ROA Other IRR onlyRADB 0 0%low visibility 1
154.58.231.0/24 No ROA Other IRR onlyRADB 0 0%low visibility 1
103.15.160.0/24 Valid None 35 5%low visibility 29
103.15.161.0/24 Valid None 35 5%low visibility 29
103.184.50.0/24 Valid Other IRR onlyRADB 672 100% 67
103.184.51.0/24 Valid Other IRR onlyRADB 669 99% 67

AS-SET

AS149672'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 12 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2001:df2:5e40::/48No ROA covers it. Add a ROA for AS149672, maxLength 48.636 of 636
Route object: RIR2001:df2:5e40::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none154.58.230.0/24No ROA covers it. Add a ROA for AS149672, maxLength 24.0 of 673
Route object: RIR154.58.230.0/24Route object only in RADB. Add it in the RIR database for the space.0 of 673
ROA: none154.58.231.0/24No ROA covers it. Add a ROA for AS149672, maxLength 24.0 of 673
Route object: RIR154.58.231.0/24Route object only in RADB. Add it in the RIR database for the space.0 of 673
Route object: none103.15.160.0/24No route object for it. Add a route object with origin AS149672 in the RIR database for the space.35 of 673
Route object: none103.15.161.0/24No route object for it. Add a route object with origin AS149672 in the RIR database for the space.35 of 673
Route object: RIR103.184.50.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.184.51.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

103.184.50.0/23RADBValid
154.58.230.0/23RADBNo ROA

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.