bgpreport

Network · data from 2026-11-12

AS136360 IsolNet Network Solution

Registry name: INSPL-IN - Isolnet Network Solution Pvt Ltd, IN · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 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
12Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS136360, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136360, 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.91.96.0/23 Valid RIR databaseAPNIC 40 6%low visibility 29
103.91.98.0/23 Valid RIR databaseAPNIC 40 6%low visibility 29
103.160.46.0/23 Valid RIR databaseAPNIC 40 6%low visibility 29
2001:df4:f680::/48 Valid RIR databaseAPNIC 39 6%low visibility 28
2001:df5:9480::/48 Valid RIR databaseAPNIC 38 6%low visibility 28
103.91.96.0/22 Valid RIR databaseAPNIC 35 5%low visibility 27
103.91.96.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
103.91.97.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
103.91.98.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
103.91.99.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
103.160.46.0/24 Valid RIR databaseAPNIC 35 5%low visibility 27
103.160.47.0/24 Valid RIR databaseAPNIC 35 5%low visibility 27

AS-SET

PeeringDB's irr_as_set for AS136360: AS136360:AS-INSPL. 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 (AS136360 isn't in the set, or no route object for AS136360 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 objectsAS136360 in itNot covered
AS136360:AS-INSPL APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE 7147320,801 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 5 are in fix.csv.

  • AS-SET: missing member5
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS136360:AS-INSPLAS136360:AS-INSPL (APNIC) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS136360:AS-INSPLAS136360:AS-INSPL (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS136360:AS-INSPLAS136360:AS-INSPL (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS136360:AS-INSPLAS136360:AS-INSPL (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS136360:AS-INSPLAS136360:AS-INSPL (APNIC) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

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