Autonomous System
AS7488
Last fetched
AS7488 is operated by CNSERVER-AP-AS - CNServer LLC, registered in US, and announces 81 prefixes to 10 BGP neighbours. AS7488 has a reputation score of 16.4 (NEUTRAL); 128 of its 25,088 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 81
- BGP neighbours
- 10
- RPKI ROAs
- 117
- MOAS conflicts
- 11
- CAIDA AS-rank
- 15,846
- Customer-cone ASNs
- 1
- Facilities
- 35
- Internet exchanges
- 3
- Customer degree
- 0
- Peer degree
- 27
- Provider degree
- 5
- 5.253.38.0/24
- 23.184.136.0/24
- 45.41.55.0/24
- 45.91.139.0/24
- 46.33.14.0/24
- 50.114.236.0/24
- 77.73.8.0/24
- 77.73.13.0/24
- 77.73.14.0/24
- 78.109.24.0/22
- 82.39.120.0/24
- 82.39.121.0/24
- 82.39.122.0/24
- 82.39.123.0/24
- 82.39.124.0/24
- 82.39.125.0/24
- 82.39.126.0/24
- 82.39.127.0/24
- 91.193.233.0/24
- 92.62.254.0/24
- 103.248.48.0/23
- 136.0.39.0/24
- 136.0.57.0/24
- 140.233.175.0/24
- 141.11.50.0/24
Infrastructure presence
Internet exchanges (3 total)
Facilities (35 total)
- CoreSite - Los Angeles (LA1) One Wilshire
- CoreSite - San Jose (SV1)
- Digital Realty Seattle SEA10
- Equinix SE2/SE3 - Seattle
- Netrality St. Louis - 900 Walnut
- CoreSite - Los Angeles (LA2)
- KOMO Plaza Seattle (Formerly Fisher Plaza)
- Netrality Houston - 1301 Fannin
- Netrality Kansas City - 1102 Grand
- Intergate West / Digital.forest / Fortress
- Coresite - Milpitas (SV2)
- Cologix MIN1
- CoreSite - Santa Clara (SV4)
- Netrality St. Louis - 210 N Tucker
- 123.NET - DC1 - 24700 Northwestern Hwy.
- Cologix MIN2
- Centersquare Seattle (SEA1-B)
- CoreSite - Santa Clara (SV3)
- H5 Data Centers Seattle
- Cologix MIN3
- CoreSite - Santa Clara (SV7)
- Patmos KC1
- Cologix MIN4
- Sabey Intergate East Building 4
- LightEdge Kansas City Subtropolis (KCI1)
Route origin authorizations
A sample of 10 of this network’s 117 ROAs.
- 103.248.48.0/23 · max length /23
- 2001:df2:c740::/48 · max length /48
- 107.149.159.0/24 · max length /24
- 136.0.34.0/24 · max length /24
- 136.0.37.0/24 · max length /24
- 136.0.39.0/24 · max length /24
- 136.0.57.0/24 · max length /24
- 136.0.73.0/24 · max length /24
- 140.235.228.0/24 · max length /24
- 140.235.229.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS7488.
Blast radius
- Announced IPv4 addresses
- 25,088
- Threat-listed addresses
- 128
- Threat density
- 0.5102 %
- Routed prefixes
- 79
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 10 of this network’s 10 BGP neighbours.
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- HURRICANE - Hurricane Electric LLC · AS6939
- AARNET-AS-AP - Australian Academic and Research Network (AARNet) · AS7575
- UNICOM-Global - China Unicom Global · AS10099
- CONVERGE-AS - Converge ICT Solutions Inc. · AS17639
- SGGS-AS-AP - SG.GS · AS24482
- WII - WholeSale Internet, Inc. · AS32097
- GCORE - G-Core Labs S.A. · AS199524
- CLOUDSINGULARITY - Tech Futures Interactive Inc. · AS394256
MOAS / hijack watch
11 announced prefixes conflict with AS7488 — another network announces the same address space. A sample:
Reputation
16.4reputation score (NEUTRAL)
AS7488 (CNSERVER-AP-AS - CNServer LLC, US) has a reputation score of 57.1 (NEUTRAL).
- Threat density
- 54.6/100
- Graph metrics
- 65.0/100
- Historical behaviour
- 75.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
- CNServer LLC
- RIR
- APNIC
- Registered
- Fri, 04 Aug 2023 05:17:15 GMT
- Abuse contact
- noc@cnserver.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS7488 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.