Autonomous System
AS6315
Last fetched
AS6315 is operated by XMISSION - XMission, L.C., registered in US, and announces 35 prefixes to 15 BGP neighbours. AS6315 has a reputation score of 9.8 (REPUTABLE); 17 of its 94,976 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 35
- BGP neighbours
- 15
- RPKI ROAs
- 29
- MOAS conflicts
- 0
- CAIDA AS-rank
- 2,911
- Customer-cone ASNs
- 9
- Facilities
- 34
- Internet exchanges
- 6
- Customer degree
- 8
- Peer degree
- 19
- Provider degree
- 7
- 44.40.48.0/24
- 45.115.61.0/24
- 68.69.160.0/20
- 102.129.219.0/24
- 103.70.38.0/24
- 103.178.164.0/23
- 166.70.0.0/16
- 185.127.92.0/24
- 192.154.7.0/24
- 198.60.22.0/24
- 198.60.80.0/22
- 198.60.84.0/24
- 198.60.104.0/22
- 198.60.108.0/24
- 198.60.108.0/23
- 198.60.109.0/24
- 198.60.110.0/24
- 198.60.113.0/24
- 198.60.114.0/24
- 198.207.196.0/24
- 199.88.179.0/24
- 199.104.120.0/21
- 204.99.129.0/24
- 204.107.178.0/24
- 204.228.128.0/19
Infrastructure presence
Internet exchanges (6 total)
Facilities (34 total)
- CoreSite - Los Angeles (LA1) One Wilshire
- CoreSite - San Jose (SV1)
- Digital Realty Seattle SEA10
- Equinix SE2/SE3 - Seattle
- CoreSite - Los Angeles (LA2)
- CoreSite - Denver (DE1)
- KOMO Plaza Seattle (Formerly Fisher Plaza)
- Intergate West / Digital.forest / Fortress
- Coresite - Milpitas (SV2)
- Cologix MIN1
- Level(3) Salt Lake City
- Tonaquint Data Center - Saint George
- CoreSite - Denver (DE2)
- XMission - Salt Lake City - Utah
- CoreSite - Santa Clara (SV4)
- EdgeConneX Salt Lake City (EDCSLC01)
- Cologix MIN2
- Flexential - Salt Lake City/Downtown (SLC04)
- Centersquare Seattle (SEA1-B)
- CoreSite - Santa Clara (SV3)
- H5 Data Centers Seattle
- Cologix MIN3
- CoreSite - Santa Clara (SV7)
- Cologix MIN4
- Sabey Intergate East Building 4
Route origin authorizations
A sample of 10 of this network’s 29 ROAs.
- 102.129.219.0/24 · max length /24
- 166.70.0.0/16 · max length /16
- 198.207.196.0/24 · max length /24
- 198.60.104.0/22 · max length /22
- 198.60.108.0/23 · max length /23
- 198.60.108.0/24 · max length /24
- 198.60.109.0/24 · max length /24
- 198.60.110.0/24 · max length /24
- 198.60.113.0/24 · max length /24
- 198.60.114.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS6315.
Blast radius
- Announced IPv4 addresses
- 94,976
- Threat-listed addresses
- 17
- Threat density
- 0.0179 %
- 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: computed.
Peering ecosystem
A sample of 15 of this network’s 15 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- LEVEL3 - Level 3 Parent, LLC · AS3356
- HURRICANE - Hurricane Electric LLC · AS6939
- SGGS-AS-AP - SG.GS · AS24482
- UTA-1 - Utah Transit Authority · AS30425
- BRMIC-MURRAY-01 - Bear River Mutual Insurance Company · AS36537
- PRECISE-NETWORKS-INC - Precise Networks, Inc. · AS40761
- TJF-HOLDINGS - TJF HOLDINGS · AS53654
- YELLOWSTONE-FIBER - UTOPIA · AS62494
- YOKO-NETWORKS - Yoko Networks Inc. · AS396109
- NS-GLOBAL - PhirePhly Design · AS398987
- PBX-SALTLAKECITY - PBXIO LLC · AS399936
- LANTASTIC - LANtastic Internet · AS401734
- ZEPHYR-BROADBAND - Zephyr Broadband, LLC · AS402028
Reputation
9.8reputation score (REPUTABLE)
AS6315 (XMISSION - XMission, L.C., US) has a reputation score of 70.5 (REPUTABLE).
- Threat density
- 75.0/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
- XMission, L.C.
- RIR
- ARIN
- Registered
- Mon, 04 Mar 1996 05:00:00 GMT
- Abuse contact
- abuse@xmission.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS6315 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.