Autonomous System
AS12008
Last fetched
AS12008 is operated by VERCARA - Vercara, LLC, registered in US, and announces 163 prefixes to 2 BGP neighbours. AS12008 has a reputation score of 13.2 (NEUTRAL); 0 of its 22,848 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 163
- BGP neighbours
- 2
- RPKI ROAs
- 152
- MOAS conflicts
- 17
- CAIDA AS-rank
- 16,060
- Customer-cone ASNs
- 1
- Facilities
- 29
- Internet exchanges
- 1
- Customer degree
- 1
- Peer degree
- 0
- Provider degree
- 2
- 37.209.196.0/24
- 64.6.64.0/24
- 64.6.65.0/24
- 74.115.29.0/24
- 120.29.253.0/24
- 156.154.34.0/24
- 156.154.54.0/24
- 156.154.55.0/24
- 156.154.64.0/24
- 156.154.65.0/24
- 156.154.66.0/24
- 156.154.67.0/24
- 156.154.68.0/24
- 156.154.69.0/24
- 156.154.71.0/24
- 156.154.72.0/24
- 156.154.73.0/24
- 156.154.74.0/24
- 156.154.74.0/23
- 156.154.75.0/24
- 156.154.86.0/24
- 156.154.86.0/23
- 156.154.87.0/24
- 156.154.102.0/24
- 156.154.104.0/24
Signals
- critical-infrastructureServes infrastructure the internet depends on operationally.
Infrastructure presence
Internet exchanges (1 total)
Facilities (29 total)
- Equinix CH1/CH2/CH4 - Chicago
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- Equinix MI1 - Miami, NOTA
- CoreSite - Los Angeles (LA1) One Wilshire
- Digital Realty Frankfurt FRA1-27
- Equinix DA3 - Dallas
- Equinix SE2/SE3 - Seattle
- Equinix SY1/SY2 - Sydney
- Digital Realty Madrid MAD1-2
- Equinix SP4 - São Paulo
- Equinix HK1 - Hong Kong
- Digital Realty Stockholm STO1-6
- Equinix SG1 - Singapore
- 165 Halsey Meet-Me Room
- Equinix LD4 - London, Slough
- Equinix TY2 - Tokyo
- Chief LY Building Taipei
- Equinix PA3 - Paris, Saint-Denis
- Teraco Johannesburg Campus, South Africa
- Equinix AM3 - Amsterdam, Science Park
- Equinix DX1 - Dubai
- Equinix BG1 - Bogota
- Equinix ME1/ME2 - Melbourne
- Vanuatu Government Datacenter
Route origin authorizations
A sample of 10 of this network’s 152 ROAs.
- 116.51.28.192/26 · max length /26
- 120.29.252.0/24 · max length /24
- 120.29.253.0/24 · max length /24
- 120.29.254.0/24 · max length /24
- 2001:dcd:1::/48 · max length /48
- 2001:dcd:2::/48 · max length /48
- 2001:dcd:3::/48 · max length /48
- 2001:dcd:4::/48 · max length /48
- 2001:dcd:5::/48 · max length /48
- 2001:dcd:6::/48 · max length /48
Upstreams
The networks that most often share an observed BGP path with AS12008.
Blast radius
- Announced IPv4 addresses
- 22,848
- Threat-listed addresses
- 0
- Threat density
- 0.0000 %
- Routed prefixes
- 91
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: clean.
Peering ecosystem
A sample of 2 of this network’s 2 BGP neighbours.
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- DIGICERT - Tiggee LLC · AS16552
MOAS / hijack watch
17 announced prefixes conflict with AS12008 — another network announces the same address space. A sample:
Reputation
13.2reputation score (NEUTRAL)
AS12008 (VERCARA - Vercara, LLC, US) has a reputation score of 63.6 (NEUTRAL).
- Threat density
- 73.2/100
- Graph metrics
- 55.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
- Vercara, LLC
- RIR
- ARIN
- Registered
- Wed, 03 Mar 1999 05:00:00 GMT
- Abuse contact
- siteprotect-sre@neustarsecurityservices.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS12008 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.