bgpreport

Network · data from 2026-11-12

AS24225 SMA-ID - ABS/SMA-INDONESIA

Registry name: SMA-ID - ABS/SMA-INDONESIA, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24225, 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.
2404:f700::/32 No ROA None 520 82% 68
103.67.242.0/23 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
103.67.240.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.67.243.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
203.160.50.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 66
203.160.50.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 66
203.160.51.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 66
103.67.240.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
103.67.241.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 66
103.67.242.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 66
203.160.48.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 66
2405:da80::/32 Valid RIR databaseAPNIC, RADB 634 100% 70

AS-SET

AS24225 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 11 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2404:f700::/32No ROA covers it. Add a ROA for AS24225, maxLength 32.520 of 636
Route object: none2404:f700::/32No route object for it. Add a route object with origin AS24225 in the RIR database for the space.520 of 636
ROA: none103.67.242.0/23No ROA covers it. Add a ROA for AS24225, maxLength 23.672 of 673
Route object: RIR103.67.242.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.67.240.0/22NTTCOM, RADBNo ROA
103.247.24.0/24RADBNo ROA
103.247.25.0/24RADBNo ROA
103.247.26.0/24RADBNo ROA
203.160.48.0/22NTTCOM, RADBNo ROA
203.160.48.0/23NTTCOM, RADBNo ROA
203.160.49.0/24NTTCOM, RADBNo 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.