Autonomous System
AS140171
Last fetched
AS140171 is operated by REISNS-AS-IN - Reis Network Solutions, registered in IN, and announces 41 prefixes to 15 BGP neighbours. AS140171 has a reputation score of 13.8 (NEUTRAL); 35 of its 8,448 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 41
- BGP neighbours
- 15
- RPKI ROAs
- 64
- MOAS conflicts
- 0
- CAIDA AS-rank
- 4,030
- Customer-cone ASNs
- 6
- Facilities
- 33
- Internet exchanges
- 2
- Customer degree
- 6
- Peer degree
- 8
- Provider degree
- 5
- 103.16.176.0/24
- 103.38.182.0/24
- 103.38.182.0/23
- 103.38.183.0/24
- 103.53.30.0/24
- 103.53.30.0/23
- 103.53.31.0/24
- 103.77.14.0/24
- 103.80.153.0/24
- 103.80.154.0/23
- 103.144.192.0/24
- 103.156.200.0/24
- 103.156.200.0/23
- 103.160.186.0/23
- 103.160.187.0/24
- 103.161.32.0/24
- 103.161.32.0/23
- 103.161.33.0/24
- 103.163.42.0/24
- 103.163.43.0/24
- 103.187.166.0/24
- 103.187.166.0/23
- 103.187.167.0/24
- 103.191.202.0/24
- 103.191.202.0/23
Routing posture
- Hijack posture score
- 0.18
- Origin mismatches
- 1
Infrastructure presence
Internet exchanges (2 total)
Facilities (33 total)
- TATA Communications Chennai
- Bharti Airtel Santhome
- Equinix MB1 - Mumbai (GPX Mumbai 1)
- Sify Greenfort - Noida
- Sify Vashi - Mumbai
- Sify Tidel-DC- Chennai
- Nxtra Data Chennai DC 1
- Netmagic Chandivali - MUM-DC05
- STT Chennai 1
- STT Chennai 2
- STT Mumbai 2
- Equinix MB2 - Mumbai (GPX Mumbai 2)
- NIXI Indore
- NIXI Bhopal
- NIXI Panaji
- Ishan Technologies Baroda
- NIXI Coimbatore
- NIXI Raipur
- Ishan Technologies Rajkot
- Ishan Technologies Surat
- Ishan Technologies Ahmedabad
- Ishan Technologies Nashik
- Ishan Technologies Raipur
- Ishan Technologies Jabalpur
- Ishan Technologies Nagpur
Route origin authorizations
A sample of 10 of this network’s 64 ROAs.
- 103.134.132.0/24 · max length /24
- 103.144.192.0/24 · max length /24
- 103.156.200.0/23 · max length /24
- 103.16.176.0/24 · max length /24
- 103.160.187.0/24 · max length /24
- 103.161.32.0/24 · max length /24
- 103.161.33.0/24 · max length /24
- 103.161.59.0/24 · max length /24
- 103.163.42.0/23 · max length /24
- 103.187.166.0/23 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS140171.
Blast radius
- Announced IPv4 addresses
- 8,448
- Threat-listed addresses
- 35
- Threat density
- 0.4143 %
- Routed prefixes
- 37
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: computed.
Peering ecosystem
A sample of 15 of this network’s 15 BGP neighbours.
- BBIL-AP - BHARTI Airtel Ltd. · AS9498
- CTRLS-AS-IN - CtrlS · AS18229
- F5 - F5 Networks SARL · AS35280
- SOIBAM-AS - Soibam Technology Private Limited · AS133300
- ULTRANET-AS - Ultranet services private limited · AS134026
- SAINETSO-AS-IN - Sai Net Solutions · AS135219
- DENETHMR-AS-IN - Denet Connect Services Pvt Ltd · AS135789
- CABLENET-AS - S S Cablenet · AS136328
- WEEBO-AS-AP - Weebo networks Pvt Ltd · AS136946
- IRINN-JAIN1-AS-IN - JAIN BROADBAND SOLUTIONS PRIVATE LIMITED · AS139514
- FASTTELE-AS - Fastcom Telelink Pvt. Ltd. · AS139529
- ULTRANOD-AS - Ultranode Communications Private Limited · AS141517
- AVISHKAR-AS-IN - Avishkar Infotech · AS150590
- KCSPLNET-AS-IN - Konark Cable System Opc Private Limited · AS153216
- IRINN-AANIRIDS-AS-IN - AANIRIDS TECHNOLOGIES PRIVATE LIMITED · AS154426
Reputation
13.8reputation score (NEUTRAL)
AS140171 (REISNS-AS-IN - Reis Network Solutions, IN) has a reputation score of 62.4 (NEUTRAL).
- Threat density
- 44.8/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 85.0/100
- Prefix age
- 20.0/100
These are reputation signals about the network as a whole, not a threat-feed verdict about a specific address.
Registration
- Registered to
- Reis Network Solutions
Threat-feed evidence
Related pages
Pivot from AS140171 into the prefixes, peers and country it routes for.
Queries
This ASN's full card — routing footprint, peers, conflicts and RIR facts.
MATCH (a:ASN {name: $asn})
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(co:COUNTRY)
OPTIONAL MATCH (a)-[:REGISTERED_BY]->(org:ORGANIZATION)
WITH a,
collect(an.name) AS operatorNames,
collect(co.name) AS countries,
collect(org.name) AS organizations
OPTIONAL MATCH (a)-[:ROUTES]->(prefix:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations,
collect(prefix.name)[0..25] AS samplePrefixes
OPTIONAL MATCH (a)-[:BGP_NEIGHBOR]-(peer:ASN)
OPTIONAL MATCH (peer)-[:HAS_NAME]->(peern:ASN_NAME)
WITH a, operatorNames, countries, organizations, samplePrefixes,
collect({asn: peer.name, operator: peern.name})[0..25] AS samplePeers
OPTIONAL MATCH (a)<-[:CONFLICTS_WITH]-(conflict:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers,
collect(conflict.name)[0..25] AS sampleConflicts
OPTIONAL MATCH (a)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts,
collect(DISTINCT sig.name) AS signals
OPTIONAL MATCH (a)-[:IX_MEMBER]->(ix:INTERNET_EXCHANGE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals,
collect({id: ix.id, name: ix.name})[0..25] AS sampleExchanges
OPTIONAL MATCH (a)-[:AS_PRESENT_AT]->(fac:FACILITY)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges,
collect({id: fac.id, name: fac.name})[0..25] AS sampleFacilities
OPTIONAL MATCH (roa:ROA)-[:ROA_AUTHORIZES_ORIGIN]->(a)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges, sampleFacilities,
collect({prefix: roa.prefix, maxLength: roa.maxLength})[0..10] AS sampleRoas
CALL { WITH a MATCH (a)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS prefixCount }
CALL { WITH a MATCH (a)-[:BGP_NEIGHBOR]-(n:ASN) RETURN count(n) AS peerCount }
CALL { WITH a MATCH (a)<-[:CONFLICTS_WITH]-(c:ANNOUNCED_PREFIX) RETURN count(c) AS conflictCount }
CALL { WITH a MATCH (a)-[:ROA_AUTHORIZES_ORIGIN]-(r:ROA) RETURN count(r) AS roaCount }
CALL { WITH a MATCH (a)-[:AS_PRESENT_AT]->(f:FACILITY) RETURN count(f) AS facilityCount }
CALL { WITH a MATCH (a)-[:IX_MEMBER]->(x:INTERNET_EXCHANGE) RETURN count(x) AS ixpCount }
RETURN a.name AS name,
a.rir AS rir,
a.orgName AS orgName,
a.asRank AS asRank,
a.coneAsns AS coneAsns,
a.conePrefixes AS conePrefixes,
a.coneAddresses AS coneAddresses,
a.registrationDate AS registrationDate,
a.reputationScore AS reputationScore,
a.reputationCategory AS reputationCategory,
a.overallThreatLevel AS overallThreatLevel,
a.abuseEmail AS abuseEmail,
a.hijackPostureScore AS hijackPostureScore,
a.hijackOriginMismatchCount AS hijackOriginMismatchCount,
a.routeLeakCount AS routeLeakCount,
a.routeLeakTypes AS routeLeakTypes,
a.degreeCustomer AS degreeCustomer,
a.degreePeer AS degreePeer,
a.degreeProvider AS degreeProvider,
operatorNames, countries, organizations,
samplePrefixes, samplePeers, sampleConflicts,
signals, sampleExchanges, sampleFacilities, sampleRoas,
prefixCount, peerCount, conflictCount, roaCount, facilityCount, ixpCountRun yourself →The five networks that most often share this ASN's observed BGP paths.
MATCH (a:ASN {name: $asn})<-[:BGP_PATH]-(b:BGP_PATH_OBSERVATION)
WITH b LIMIT 200
MATCH (b)-[:BGP_PATH]->(up:ASN)
WHERE up.name <> $asn
WITH up.name AS asn, count(*) AS observations
ORDER BY observations DESC
LIMIT 5
RETURN asn, observationsRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.