Autonomous System
AS400318
Last fetched
AS400318 is operated by VERSA-01 - Versa Networks, Inc., registered in US, and announces 30 prefixes to 11 BGP neighbours. AS400318 has a reputation score of 7.3 (REPUTABLE); 0 of its 7,168 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 30
- BGP neighbours
- 11
- RPKI ROAs
- 373
- MOAS conflicts
- 0
- CAIDA AS-rank
- 19,633
- Customer-cone ASNs
- 1
- Facilities
- 79
- Internet exchanges
- 14
- Customer degree
- 0
- Peer degree
- 56
- Provider degree
- 12
- 49.0.56.0/24
- 49.0.57.0/24
- 49.0.58.0/24
- 49.0.59.0/24
- 49.0.60.0/24
- 49.0.61.0/24
- 49.0.62.0/24
- 49.0.63.0/24
- 64.65.16.0/24
- 64.65.17.0/24
- 64.65.18.0/24
- 64.65.19.0/24
- 64.65.20.0/24
- 64.65.21.0/24
- 64.65.22.0/24
- 64.65.23.0/24
- 103.36.54.0/24
- 103.247.56.0/24
- 103.247.57.0/24
- 103.247.58.0/24
- 185.16.1.0/24
- 193.57.228.0/24
- 193.57.229.0/24
- 193.57.230.0/24
- 208.54.22.0/24
Infrastructure presence
Internet exchanges (14 total)
Facilities (79 total)
- Equinix HK1 - Hong Kong
- Equinix TY1 - Tokyo
- Equinix SY1/SY2 - Sydney
- Equinix FR5 - Frankfurt, KleyerStrasse
- Equinix LD8 - London, Docklands
- Equinix NY9 - New York, 111 8th Avenue
- Equinix NY2/NY4/NY5/NY6 - New York, Secaucus
- Equinix MI1 - Miami, NOTA
- Equinix TR1 - Toronto
- Equinix CH1/CH2/CH4 - Chicago
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- Equinix NY1 - New York, Newark
- Equinix DA1 - Dallas
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- Equinix FR7 - Frankfurt, Gutleutstrasse
- Equinix DA3 - Dallas
- Equinix AM7 - Amsterdam, Kuiperberweg
- Equinix SV2 - Silicon Valley, Santa Clara
- Equinix LD4 - London, Slough
- Digital Realty CHI (350 E Cermak)
- Equinix FR2 - Frankfurt, North
- Equinix TY2 - Tokyo
- Equinix SG1 - Singapore
- Equinix AM1/AM2 - Amsterdam, Luttenbergweg
- Equinix ME5 - Melbourne (formerly Metronode Melbourne 1)
Route origin authorizations
A sample of 10 of this network’s 373 ROAs.
- 103.247.56.0/22 · max length /28
- 103.36.54.0/23 · max length /29
- 2401:daa0:55::/48 · max length /48
- 2401:daa0:57::/48 · max length /48
- 49.0.56.0/21 · max length /21
- 49.0.56.0/24 · max length /24
- 49.0.57.0/24 · max length /24
- 49.0.58.0/24 · max length /24
- 49.0.59.0/24 · max length /24
- 49.0.60.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS400318.
Blast radius
- Announced IPv4 addresses
- 7,168
- Threat-listed addresses
- 0
- Threat density
- 0.0000 %
- Routed prefixes
- 28
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 11 of this network’s 11 BGP neighbours.
- ASN-TELSTRA - Telstra Limited · AS1221
- UNITAS - Unitas Global · AS1828
- KDDI - KDDI CORPORATION · AS2516
- LEVEL3 - Level 3 Parent, LLC · AS3356
- HURRICANE - Hurricane Electric LLC · AS6939
- OPTUSCOM-AS01-AU - SingTel Optus Pty Ltd · AS7474
- SIFY-AS-IN - Sify Limited · AS9583
- ZEN-ECN - Zenlayer Inc · AS21859
- T-MOBILE-AS21928 - T-Mobile USA, Inc. · AS21928
- SLT-NW2 - Sri Lanka Telecom Ltd · AS138984
- YOTTA - YOTTA NETWORK SERVICES PRIVATE LIMITED · AS140641
Reputation
7.3reputation score (REPUTABLE)
AS400318 (VERSA-01 - Versa Networks, Inc., US) has a reputation score of 78.3 (REPUTABLE).
- Threat density
- 90.0/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
- Versa Networks, Inc.
- RIR
- ARIN
- Registered
- Fri, 17 Dec 2021 16:46:39 GMT
- Abuse contact
- arin-admin@versa-networks.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS400318 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.