Autonomous System
AS35985
Last fetched
AS35985 is operated by ONERINGNET-ATL-1 - One Ring Networks, Inc., registered in US, and announces 45 prefixes to 18 BGP neighbours. AS35985 has a reputation score of 8.4 (REPUTABLE); 8 of its 135,168 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 45
- BGP neighbours
- 18
- RPKI ROAs
- 8
- MOAS conflicts
- 0
- CAIDA AS-rank
- 1,931
- Customer-cone ASNs
- 16
- Facilities
- 40
- Internet exchanges
- 5
- Customer degree
- 14
- Peer degree
- 45
- Provider degree
- 2
- 24.41.90.0/24
- 24.235.0.0/24
- 64.191.128.0/18
- 64.211.212.0/22
- 64.238.40.0/21
- 66.17.93.0/24
- 66.146.160.0/19
- 66.187.176.0/20
- 66.209.96.0/19
- 67.211.0.0/19
- 67.220.160.0/20
- 69.169.192.0/19
- 72.21.224.0/19
- 72.34.64.0/19
- 72.249.216.0/21
- 72.250.160.0/20
- 98.142.16.0/20
- 104.167.183.0/24
- 142.214.244.0/22
- 199.85.84.0/22
- 199.96.240.0/22
- 204.9.56.0/23
- 204.9.61.0/24
- 204.9.62.0/24
- 204.48.120.0/22
Infrastructure presence
Internet exchanges (5 total)
Facilities (40 total)
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- Equinix DA1 - Dallas
- CoreSite - San Jose (SV1)
- CoreSite - Los Angeles (LA1) One Wilshire
- Equinix DA3 - Dallas
- Digital Realty ATL13 - Atlanta
- Digital Realty PHX10 (120 E Van Buren)
- CoreSite - Los Angeles (LA2)
- Digital Realty DFW (2323 Bryan St)
- Equinix DA - Dallas (previously Infomart Dallas)
- Iron Mountain Data Center - Phoenix (AZP-1)
- Coresite - Milpitas (SV2)
- Equinix CU1/CU2/CU3/CU4 - Culpeper
- PhoenixNAP
- CyrusOne Dallas (Carrollton)
- CoreSite - Santa Clara (SV4)
- EdgeConneX Phoenix (EDCPHX01)
- Flexential - Dallas/Downtown (DAL01)
- Flexential - Phoenix (PHX01)
- Equinix DA6 - Dallas
- Cologix DAL2
- Cologix DAL1
- DataBank Dallas (DFW5)
- Equinix DA2 - Dallas
- Centersquare Phoenix (PHX1)
Route origin authorizations
A sample of 8 of this network’s 8 ROAs.
Upstreams
The networks that most often share an observed BGP path with AS35985.
Blast radius
- Announced IPv4 addresses
- 135,168
- Threat-listed addresses
- 8
- Threat density
- 0.0059 %
- Routed prefixes
- 41
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 18 of this network’s 18 BGP neighbours.
- LEVEL3 - Level 3 Parent, LLC · AS3356
- ZAYO-6461 - Zayo Bandwidth · AS6461
- HURRICANE - Hurricane Electric LLC · AS6939
- AARNET-AS-AP - Australian Academic and Research Network (AARNet) · AS7575
- Etisalat-AS - EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC · AS8966
- PLANNET-OC-01 - PlanNet LLC · AS18685
- NEXTCO-AS - Nextera Communications LLC · AS22402
- SGGS-AS-AP - SG.GS · AS24482
- ENGINEERING-ASN1 - CONVERGEONE HOLDINGS, INC. · AS27580
- BROADASPECT - BroadAspect · AS30259
- TELCENTREX - Telcentrex LLC · AS54313
- PL-BGP - Prime-Line Products Company · AS62829
- VALOR-COMMUNICATION-INC-INDUSTRY - VALOR COMMUNICATION, INC. · AS394246
- 1ST-TECH - XPRESSBET INC. · AS394253
- USTX04 - 1A Smart Start LLC · AS397690
- ELN-ATL-HQ - EarthLink · AS397866
- LAKESHORE-LEARNING - Lakeshore Learning Materials · AS398185
- ONERINGNETWORKS - Melissa's Produce · AS400957
Reputation
8.4reputation score (REPUTABLE)
AS35985 (ONERINGNET-ATL-1 - One Ring Networks, Inc., US) has a reputation score of 74.7 (REPUTABLE).
- Threat density
- 87.1/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
- One Ring Networks, Inc.
- RIR
- ARIN
- Registered
- Mon, 02 May 2005 18:16:47 GMT
- Abuse contact
- abuse@oneringnetworks.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS35985 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.