Autonomous System
AS13984
Last fetched
AS13984 is operated by SD-DATA-CENTER - SD Data Center, registered in US, and announces 33 prefixes to 25 BGP neighbours. AS13984 has a reputation score of 9.3 (REPUTABLE); 0 of its 28,160 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 33
- BGP neighbours
- 25
- RPKI ROAs
- 30
- MOAS conflicts
- 0
- CAIDA AS-rank
- 2,402
- Customer-cone ASNs
- 12
- Facilities
- 55
- Internet exchanges
- 6
- Customer degree
- 9
- Peer degree
- 115
- Provider degree
- 10
- 8.34.27.0/24
- 63.144.240.0/24
- 74.117.144.0/22
- 103.102.8.0/22
- 162.217.148.0/22
- 164.153.0.0/20
- 173.227.128.0/24
- 173.227.128.0/22
- 193.25.186.0/23
- 205.149.134.0/23
- 205.149.128.0/20
- 205.149.143.0/24
- 206.124.171.0/24
- 206.124.173.0/24
- 206.124.190.0/24
- 208.234.168.0/23
- 209.114.192.0/19
- 209.151.192.0/22
- 209.151.197.0/24
- 209.151.196.0/22
- 209.151.198.0/24
- 209.151.199.0/24
- 209.151.200.0/22
- 209.151.217.0/24
- 209.151.218.0/23
Infrastructure presence
Internet exchanges (6 total)
Facilities (55 total)
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- Equinix MI1 - Miami, NOTA
- CoreSite - San Jose (SV1)
- NIKHEF Amsterdam
- CoreSite - Los Angeles (LA1) One Wilshire
- Equinix AM7 - Amsterdam, Kuiperberweg
- Global Switch Amsterdam
- Digital Realty AMS17 - Amsterdam
- Digital Realty AMS3/5/7/8/10 - Amsterdam
- Digital Realty AMS9 - Amsterdam
- Equinix SY1/SY2 - Sydney
- iM Critical Miami
- DigiCo Sydney SYD1 (formerly Global Switch Australia)
- CoreSite - Los Angeles (LA2)
- Iron Mountain Data Center - Amsterdam (AMS-1)
- Equinix AM1/AM2 - Amsterdam, Luttenbergweg
- Equinix MI2 - Miami
- 365 Data Centers Boca Raton (BC1)
- QTS Miami (MIA1)
- 365 Data Centers Ft. Lauderdale (FLL)
- Coresite - Milpitas (SV2)
- CoreSite - Miami (MI1)
- ColoHouse Miami
- Equinix CU1/CU2/CU3/CU4 - Culpeper
- Smartdc Rotterdam
Route origin authorizations
A sample of 10 of this network’s 30 ROAs.
- 103.102.8.0/22 · max length /22
- 2401:dac0::/32 · max length /32
- 162.217.148.0/22 · max length /22
- 164.153.0.0/20 · max length /24
- 204.246.24.0/24 · max length /24
- 204.246.26.0/24 · max length /24
- 205.149.128.0/20 · max length /32
- 205.149.134.0/23 · max length /23
- 206.124.171.0/24 · max length /24
- 206.124.173.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS13984.
Blast radius
- Announced IPv4 addresses
- 28,160
- 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 25 of this network’s 25 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- SURFNET-NL - SURF B.V. · AS1103
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- LEVEL3 - Level 3 Parent, LLC · AS3356
- GALAXY - Galaxy Networks (division of Kolacom, Inc.) · AS5702
- ZAYO-6461 - Zayo Bandwidth · AS6461
- HURRICANE - Hurricane Electric LLC · AS6939
- ATT-INTERNET4 - AT&T Enterprises, LLC · AS7018
- SAGENET - SageNet LLC · AS7285
- AARNET-AS-AP - Australian Academic and Research Network (AARNet) · AS7575
- GOGO - Gogo Business Aviation LLC · AS11167
- CONVERGE-AS - Converge ICT Solutions Inc. · AS17639
- SATCOM-DIRECT-INC - Satcom Direct Inc. · AS23137
- SGGS-AS-AP - SG.GS · AS24482
- BHN-33363 - Charter Communications, Inc · AS33363
- SD GOVERNMENT-INC - SD Government · AS36614
- Virtual Technologies & Solutions - Virtual Technologies & Solutions · AS37721
- TKSWF-AS - Stadtwerke Feldkirch · AS48362
- SATCOM-DIRECT-INC - Satcom Direct Inc. · AS54238
- WEBBYENT - Webby Enterprises LLC · AS63031
- YTHING-NET-1 - Ything LLC · AS63183
- VETTA - Vetta Group · AS64073
- PATH-NETWORK - Path Network, Inc. · AS396998
- INTELLIVOICE - IntelliVoice · AS398737
Reputation
9.3reputation score (REPUTABLE)
AS13984 (SD-DATA-CENTER - SD Data Center, US) has a reputation score of 72.0 (REPUTABLE).
- Threat density
- 90.0/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 60.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
- SD Data Center
- RIR
- ARIN
- Registered
- Wed, 20 Sep 2006 20:11:38 GMT
- Abuse contact
- support@sddatacenter.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS13984 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.