bgpreport

Network · data from 2026-11-12

AS138876 Saranaindo

Registry name: IDNIC-SARANAINDO-AS-ID - CV. Saranaindo, ID · PeeringDB

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

Announced routes

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

103.140.90.0/23 Valid Other IRR onlyALTDB 673 100% 66
103.140.90.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 68
103.140.91.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 68
2001:df0:b580::/48 Valid Other IRR onlyALTDB 34 5%low visibility 28

AS-SET

PeeringDB's irr_as_set for AS138876: AS-SARANAINDO. 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 (AS138876 isn't in the set, or no route object for AS138876 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 objectsAS138876 in itNot covered
AS-SARANAINDO ALTDB 7135 Yes 0

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

  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: RIR103.140.90.0/23Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.140.90.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.140.91.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2001:df0:b580::/48Route object only in ALTDB. Add it in the RIR database for the space.34 of 636

Route objects not announced

Every route object with origin AS138876 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.