Autonomous System
AS216071
Last fetched
AS216071 is operated by VDSINA - SERVERS TECH FZCO, registered in AE, and announces 615 prefixes to 14 BGP neighbours. AS216071 has a reputation score of 17.2 (NEUTRAL); 743 of its 156,416 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 615
- BGP neighbours
- 14
- RPKI ROAs
- 617
- MOAS conflicts
- 0
- CAIDA AS-rank
- 13,297
- Customer-cone ASNs
- 1
- Facilities
- 60
- Internet exchanges
- 3
- Customer degree
- 0
- Peer degree
- 84
- Provider degree
- 6
- 5.35.32.0/24
- 5.35.33.0/24
- 5.35.34.0/24
- 5.35.36.0/24
- 5.35.37.0/24
- 5.35.38.0/24
- 5.35.39.0/24
- 5.35.44.0/24
- 5.35.45.0/24
- 5.35.46.0/24
- 5.35.47.0/24
- 5.35.68.0/24
- 5.35.69.0/24
- 5.35.70.0/24
- 5.35.71.0/24
- 46.149.72.0/24
- 46.149.73.0/24
- 46.149.74.0/24
- 46.149.75.0/24
- 46.149.76.0/24
- 46.149.77.0/24
- 46.149.78.0/24
- 46.149.79.0/24
- 46.151.24.0/24
- 46.151.25.0/24
Infrastructure presence
Facilities (60 total)
- NIKHEF Amsterdam
- Telehouse - London (Docklands North)
- Speedbone Berlin
- Equinix SK1 - Stockholm, Bromma
- Moscow M9
- Digital Realty AMS9 - Amsterdam
- Telehouse - Paris 2 (Voltaire - Léon Frot)
- Digital Realty AMS17 - Amsterdam
- Equinix AM7 - Amsterdam, Kuiperberweg
- Equinix FR5 - Frankfurt, KleyerStrasse
- Digital Realty Frankfurt FRA1-27
- Digital Realty VIE1/2 - Vienna
- Global Switch Amsterdam
- Digital Realty AMS3/5/7/8/10 - Amsterdam
- CE Colo Prague
- Digital Realty Stockholm STO1-6
- Digital Realty Marseille MRS1/2/3/4
- NewTelco Kiev
- Iron Mountain Data Center - Amsterdam (AMS-1)
- Equinix AM1/AM2 - Amsterdam, Luttenbergweg
- Linxdatacenter (Moscow)
- Dataplex Budapest
- Ucomline Kiev
- Equinix WA1 - Warsaw, Centrum LIM
- LIM Warsaw
Route origin authorizations
A sample of 10 of this network’s 617 ROAs.
- 109.107.164.0/24 · max length /24
- 109.107.165.0/24 · max length /24
- 109.107.166.0/24 · max length /24
- 109.107.167.0/24 · max length /24
- 109.107.172.0/24 · max length /24
- 109.107.173.0/24 · max length /24
- 109.107.174.0/24 · max length /24
- 109.107.175.0/24 · max length /24
- 109.107.176.0/24 · max length /24
- 109.107.177.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS216071.
Blast radius
- Announced IPv4 addresses
- 156,416
- Threat-listed addresses
- 743
- Threat density
- 0.4750 %
- Routed prefixes
- 611
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 14 of this network’s 14 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- HURRICANE - Hurricane Electric LLC · AS6939
- NEO-ASN - Zayo Infrastructure France SA · AS8218
- RETN-AS - RETN Limited · AS9002
- SGGS-AS-AP - SG.GS · AS24482
- GNM-AS - Global Network Management Inc · AS31500
- CORE-BACKBONE - Core-Backbone GmbH · AS33891
- Virtual Technologies & Solutions - Virtual Technologies & Solutions · AS37721
- StormNetworks - Storm Networks LLC · AS43298
- TRUENETWORK - Truenetwork LLC · AS49673
- Serverius-as - Serverius Holding B.V. · AS50673
- GIGAHOST - Gigahost AS · AS56655
- STORMWALL-AS - StormWall s.r.o. · AS59796
- gibirnet-tr - GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI · AS208972
Reputation
17.2reputation score (NEUTRAL)
AS216071 (VDSINA - SERVERS TECH FZCO, AE) has a reputation score of 55.5 (NEUTRAL).
- Threat density
- 32.2/100
- Graph metrics
- 90.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
- SERVERS TECH FZCO
- RIR
- RIPE
- Registered
- Mon, 30 Oct 2023 12:38:32 GMT
- Abuse contact
- abuse@vdsina.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS216071 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.