Network · data from 2026-11-12
AS140171 Reis Network solutions
Registry name: REISNS-AS-IN - Reis Network Solutions, IN · PeeringDB
42IPv4 routes
78.6% RPKI valid · 78.6% with a route object
4IPv6 routes
100.0% RPKI valid · 100.0% with a route object
2RPKI invalid
2 origin · 0 maxLength
7No ROA
9 with no route object for this origin
12Low visibility
seen by under 10% of full-table peers
24Route objects not announced
registered with origin AS140171, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS140171, 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.
| 154.3.78.0/23 | Invalid: origin | None | 135 20% |
| 151.158.226.0/23 | Invalid: origin | Other origin only | 2 0%low visibility |
| 103.53.30.0/23 | No ROA | None | 672 100% |
| 103.80.154.0/23 | No ROA | Other origin only | 672 100% |
| 103.160.186.0/23 | No ROA | None | 672 100% |
| 103.161.32.0/23 | No ROA | None | 672 100% |
| 103.209.62.0/23 | No ROA | None | 672 100% |
| 103.80.154.0/24 | No ROA | Other origin only | 671 100% |
| 160.187.82.0/23 | No ROA | None | 2 0%low visibility |
| 103.16.176.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.38.182.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.38.182.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.38.183.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.77.14.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.80.153.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.144.192.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.156.200.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.156.200.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.156.201.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.160.187.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.161.32.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.163.42.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.163.43.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.187.166.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.191.202.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.209.174.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.209.175.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 138.252.110.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.187.82.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.187.83.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 163.227.103.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.61.108.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.191.203.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2001:df1:1fc0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df1:20c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:c5a0::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 103.209.62.0/24 | Valid | RIR databaseAPNIC | 43 6%low visibility |
| 103.209.63.0/24 | Valid | RIR databaseAPNIC | 43 6%low visibility |
| 2001:df1:2040::/48 | Valid | RIR databaseAPNIC | 42 7%low visibility |
| 103.191.202.0/24 | Valid | RIR databaseAPNIC | 37 5%low visibility |
| 103.53.30.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 103.53.31.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 103.161.33.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 103.187.166.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 103.187.167.0/24 | Valid | RIR databaseAPNIC | 35 5%low visibility |
| 103.163.42.0/23 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS140171: AS140171:AS-REISNS. 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 (AS140171 isn't in the set, or no route object for AS140171 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.
| Name | Database | ASNs | Sets | AS140171 in it | Not covered |
|---|---|---|---|---|---|
| AS140171:AS-REISNS | RADBlists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE | 714 | 73 | Yes | 9 |
| APNIC (also)lists itself further down5 member sets in no database: AS-6186, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE, AS215228:AS-WSNL | 471 | 51 | Yes | 9 |
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 47 are in fix.csv.
- ROA: origin2
- ROA: none7
- Route object: none9
- AS-SET: missing member5
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 154.3.78.0/23 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS140171 should announce it, add a ROA for AS140171. |
| Route object: none | 154.3.78.0/23 | No route object for it. Add a route object with origin AS140171 in the RIR database for the space. |
| ROA: origin | 151.158.226.0/23 | ROAs covering it name AS152154, not AS140171. If AS140171 should announce it, add a ROA for AS140171. |
| Route object: none | 151.158.226.0/23 | Route objects for it name AS152154. Add a route object with origin AS140171 in the RIR database for the space. |
| ROA: none | 103.53.30.0/23 | No ROA covers it. Add a ROA for AS140171, maxLength 23. |
| Route object: none | 103.53.30.0/23 | No route object for it. Add a route object with origin AS140171 in the RIR database for the space. |
| ROA: none | 103.80.154.0/23 | No ROA covers it. Add a ROA for AS140171, maxLength 23. |
| Route object: none | 103.80.154.0/23 | Route objects for it name AS133250. Add a route object with origin AS140171 in the RIR database for the space. |
| ROA: none | 103.160.186.0/23 | No ROA covers it. Add a ROA for AS140171, maxLength 23. |
| Route object: none | 103.160.186.0/23 | No route object for it. Add a route object with origin AS140171 in the RIR database for the space. |
| ROA: none | 103.161.32.0/23 | No ROA covers it. Add a ROA for AS140171, maxLength 23. |
| Route object: none | 103.161.32.0/23 | No route object for it. Add a route object with origin AS140171 in the RIR database for the space. |
| ROA: none | 103.209.62.0/23 | No ROA covers it. Add a ROA for AS140171, maxLength 23. |
| Route object: none | 103.209.62.0/23 | No route object for it. Add a route object with origin AS140171 in the RIR database for the space. |
| ROA: none | 103.80.154.0/24 | No ROA covers it. Add a ROA for AS140171, maxLength 24. |
| Route object: none | 103.80.154.0/24 | Route objects for it name AS133250. Add a route object with origin AS140171 in the RIR database for the space. |
| ROA: none | 160.187.82.0/23 | No ROA covers it. Add a ROA for AS140171, maxLength 23. |
| Route object: none | 160.187.82.0/23 | No route object for it. Add a route object with origin AS140171 in the RIR database for the space. |
| AS-SET: missing member | AS140171:AS-REISNS | AS140171:AS-REISNS (RADB) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | AS140171:AS-REISNS | AS140171:AS-REISNS (RADB) lists AS-HNSISP-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | AS140171:AS-REISNS | AS140171:AS-REISNS (RADB) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | AS140171:AS-REISNS | AS140171:AS-REISNS (RADB) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | AS140171:AS-REISNS | AS140171:AS-REISNS (RADB) lists AS214174:AS-RIPE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS140171 whose prefix no peer sees AS140171 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.66.18.0/24 | APNIC | Valid |
| 103.80.152.0/23 | APNIC | Valid |
| 103.134.132.0/24 | APNIC | Valid |
| 103.161.59.0/24 | APNIC | Valid |
| 103.163.127.0/24 | APNIC | No ROA |
| 103.209.174.0/23 | APNIC | Valid |
| 163.223.213.0/24 | APNIC | Invalid: origin |
| 163.227.102.0/24 | APNIC | Valid |
| 2001:df0:cf80::/48 | APNIC | Valid |
| 2001:df1:2240::/48 | APNIC | Valid |
| 2001:df1:22c0::/48 | APNIC | Valid |
| 2001:df1:2740::/48 | APNIC | Valid |
| 2001:df1:8740::/48 | APNIC | Valid |
| 2001:df2:240::/47 | APNIC | Valid |
| 2001:df2:240::/49 | APNIC | Valid |
| 2001:df2:240:8000::/49 | APNIC | Valid |
| 2001:df2:241::/48 | APNIC | Valid |
| 2001:df2:241::/49 | APNIC | Valid |
| 2001:df2:241:8000::/49 | APNIC | Valid |
| 2001:df3:440::/48 | APNIC | Valid |
| 2001:df3:3840::/48 | APNIC | Valid |
| 2001:df4:1a40::/48 | APNIC | Valid |
| 2001:df6:1780::/48 | APNIC | No ROA |
| 2001:df6:91c0::/48 | APNIC | Valid |
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.