Autonomous System
AS906
Last fetched
AS906 is operated by DMIT - DMIT Cloud Services, registered in US, and announces 240 prefixes to 16 BGP neighbours. AS906 has a reputation score of 14.7 (NEUTRAL); 80 of its 80,384 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 240
- BGP neighbours
- 16
- RPKI ROAs
- 26
- MOAS conflicts
- 5
- CAIDA AS-rank
- 2,345
- Customer-cone ASNs
- 12
- Facilities
- 39
- Internet exchanges
- 6
- Customer degree
- 8
- Peer degree
- 43
- Provider degree
- 7
- 45.59.184.0/24
- 45.59.185.0/24
- 45.59.186.0/24
- 45.59.187.0/24
- 45.88.195.0/24
- 64.186.224.0/24
- 64.186.225.0/24
- 64.186.226.0/24
- 64.186.227.0/24
- 64.186.228.0/24
- 64.186.229.0/24
- 64.186.230.0/24
- 64.186.231.0/24
- 64.186.224.0/20
- 64.186.232.0/24
- 64.186.233.0/24
- 64.186.234.0/24
- 64.186.235.0/24
- 64.186.236.0/24
- 64.186.237.0/24
- 64.186.238.0/24
- 64.186.239.0/24
- 64.186.240.0/24
- 64.186.241.0/24
- 64.186.242.0/24
Infrastructure presence
Internet exchanges (6 total)
Facilities (39 total)
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- Equinix LA1 - Los Angeles
- CoreSite - Los Angeles (LA1) One Wilshire
- Telehouse – TOKYO Otemachi (KDDI Otemachi)
- Equinix HK1 - Hong Kong
- MEGA-i (iAdvantage Hong Kong)
- Equinix SG1 - Singapore
- CoreSite - Los Angeles (LA2)
- Digital Realty LAX (600 W 7th)
- Equinix TY2 - Tokyo
- NTT DATA Otemachi Bldg
- Digital Edge TYO2 (ComSpace 1) - Tokyo
- Equinix SG2 - Singapore
- AT TOKYO (CC1/CC2)
- CUHK
- Equinix HK2 - Hong Kong
- COLT in Asia Tokyo Data Center 1 (TDC1)
- Equinix TY4 - Tokyo
- Equinix SG3 - Singapore
- Equinix HK3 - Hong Kong
- MEGA Two (iAdvantage Hong Kong)
- Equinix TY8 - Tokyo
- FRT iDC Okinawa
- Colt DC Tokyo II
- Telehouse - Hong Kong CCC (HKCOLO TKO)
Route origin authorizations
A sample of 10 of this network’s 26 ROAs.
- 103.117.100.0/22 · max length /24
- 103.135.248.0/22 · max length /22
- 103.135.248.0/24 · max length /24
- 103.135.249.0/24 · max length /24
- 103.135.250.0/24 · max length /24
- 103.135.251.0/24 · max length /24
- 2403:18c0::/32 · max length /48
- 131.143.180.0/22 · max length /24
- 170.39.22.0/24 · max length /24
- 179.253.224.0/19 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS906.
Blast radius
- Announced IPv4 addresses
- 80,384
- Threat-listed addresses
- 80
- Threat density
- 0.0995 %
- Routed prefixes
- 229
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 16 of this network’s 16 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- HYONIX - Hyonix · AS931
- TWELVE99 - Arelion Sweden AB · AS1299
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- HKIX-RS1 - Hong Kong Internet Exchange--Route Server 1 · AS4635
- HURRICANE - Hurricane Electric LLC · AS6939
- SGGS-AS-AP - SG.GS · AS24482
- IT7NET - IT7 Networks Inc · AS25820
- DMIT-SERVICES - DMIT Cloud Services · AS32519
- NEWMEDIAEXPRESS-AS-AP - NewMedia Express Pte Ltd · AS38001
- DMITINC-AS-AP - DMIT Inc · AS132110
- GSLNETWORKS-AS-AP - GSL Networks Pty LTD · AS137409
- ZMTO - ZMTO Technologies OU · AS210661
- BYTEVIRTLLC - ByteVirt LLC · AS212336
- ONECABLE - OneCable Network LLC · AS401560
MOAS / hijack watch
5 announced prefixes conflict with AS906 — another network announces the same address space. A sample:
Reputation
14.7reputation score (NEUTRAL)
AS906 (DMIT - DMIT Cloud Services, US) has a reputation score of 60.5 (NEUTRAL).
- Threat density
- 46.6/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
- DMIT Cloud Services
- RIR
- ARIN
- Registered
- Fri, 10 Jun 2022 18:16:03 GMT
- Abuse contact
- abuse@dmit.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS906 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.