bgpreport

Network · data from 2026-11-12

AS149315 SOLNET INDONESIA AS149315

Registry name: SOLNET-ID - PT Solnet Indonesia, ID · PeeringDB

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

Announced routes

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

2407:7c0:1000::/48 No ROA None 636 100% 70
2407:7c0:1493::/48 No ROA None 636 100% 70
103.184.16.0/24 Valid Other IRR onlyRADB 673 100% 69
103.184.17.0/24 Valid Other IRR onlyRADB 673 100% 69
103.186.168.0/24 Valid Other IRR onlyRADB 673 100% 69
103.186.169.0/24 Valid Other IRR onlyRADB 673 100% 69
66.150.244.0/24 Valid RIR databaseAPNIC, RADB 673 100% 70
66.150.245.0/24 Valid RIR databaseAPNIC, RADB 4 1%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS149315: AS149315:AS-SET-SOLNET-ID. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS149315 isn't in the set, or no route object for AS149315 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS149315 in itNot covered
AS149315:AS-SET-SOLNET-ID RADB 1111 Yes 2

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

  • ROA: none2
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2407:7c0:1000::/48No ROA covers it. Add a ROA for AS149315, maxLength 48.636 of 636
Route object: none2407:7c0:1000::/48No route object for it. Add a route object with origin AS149315 in the RIR database for the space.636 of 636
ROA: none2407:7c0:1493::/48No ROA covers it. Add a ROA for AS149315, maxLength 48.636 of 636
Route object: none2407:7c0:1493::/48No route object for it. Add a route object with origin AS149315 in the RIR database for the space.636 of 636
Route object: RIR103.184.16.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.184.17.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.186.168.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.186.169.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

103.186.168.0/23RADBValid
2407:7c0:200::/40RADBValid
2407:7c0:200::/48RADBValid
2407:7c0:201::/48RADBValid
2407:7c0:202::/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.