bgpreport

Network · data from 2026-11-12

AS142394 PT Cahaya Solusindo Internusa

Registry name: CSNET-AS-ID - PT Cahaya Solusindo Internusa, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS142394, 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.164.11.0/24 No ROA Other origin only 1 0%low visibility 1
103.172.196.0/24 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS142394: AS-CSNET. 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 (AS142394 isn't in the set, or no route object for AS142394 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 objectsAS142394 in itNot covered
AS-CSNET AFRINIC 1112 No 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 9 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • AS-SET: own ASN1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.164.11.0/24No ROA covers it. Add a ROA for AS142394, maxLength 24.1 of 673
Route object: none103.164.11.0/24Route objects for it name AS141900. Add a route object with origin AS142394 in the RIR database for the space.1 of 673
ROA: none103.172.196.0/24No ROA covers it. Add a ROA for AS142394, maxLength 24.670 of 673
Route object: RIR103.172.196.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
AS-SET: own ASNAS-CSNETAS142394 isn't in AS-CSNET (AFRINIC) once expanded. Add AS142394 to it.

Route objects not announced

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

103.164.10.0/24RADBNo ROA
103.172.196.0/23RADBNo ROA
103.179.182.0/23RADBNo ROA
2001:df0:5d40::/48RADBNo 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.