Autonomous System
AS200000
Last fetched
AS200000 is operated by Ukraine-AS - Hosting Ukraine LTD, registered in UA, and announces 48 prefixes to 9 BGP neighbours. AS200000 has a reputation score of 14.9 (NEUTRAL); 27 of its 38,656 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 48
- BGP neighbours
- 9
- RPKI ROAs
- 53
- MOAS conflicts
- 0
- CAIDA AS-rank
- 8,305
- Customer-cone ASNs
- 2
- Facilities
- 36
- Internet exchanges
- 2
- Customer degree
- 1
- Peer degree
- 18
- Provider degree
- 8
- 37.139.64.0/21
- 45.154.218.0/24
- 46.247.80.0/21
- 91.206.200.0/23
- 91.222.136.0/22
- 109.205.96.0/21
- 173.242.48.0/20
- 185.25.116.0/22
- 185.39.224.0/22
- 185.65.244.0/22
- 185.68.16.0/22
- 185.69.152.0/22
- 185.104.44.0/22
- 185.124.8.0/22
- 185.149.40.0/22
- 185.209.168.0/22
- 185.225.212.0/22
- 185.226.24.0/22
- 185.233.36.0/22
- 185.233.40.0/22
- 185.233.44.0/22
- 185.233.116.0/22
- 185.233.120.0/22
- 185.233.136.0/22
- 185.233.152.0/22
Infrastructure presence
Facilities (36 total)
- NIKHEF Amsterdam
- Equinix AM7 - Amsterdam, Kuiperberweg
- Equinix FR5 - Frankfurt, KleyerStrasse
- Digital Realty Frankfurt FRA1-27
- Telehouse - Paris 2 (Voltaire - Léon Frot)
- Equinix LD8 - London, Docklands
- Equinix NY2/NY4/NY5/NY6 - New York, Secaucus
- Digital Realty Madrid MAD1-2
- Equinix HK1 - Hong Kong
- Equinix FR7 - Frankfurt, Gutleutstrasse
- CE Colo Prague
- euNetworks Amsterdam
- Equinix AM1/AM2 - Amsterdam, Luttenbergweg
- NewTelco Kiev
- Sitel Bratislava
- LIM Warsaw
- Equinix WA1 - Warsaw, Centrum LIM
- TELEPOINT Sofia Centre
- Equinix FR4 - Frankfurt, West
- Equinix PA6 - Paris, Condorcet
- Equinix AM3 - Amsterdam, Science Park
- Equinix AM5 - Amsterdam, Schepenbergweg
- Equinix AM11 - Amsterdam, Lemelerbergweg
- Equinix SO1 - Sofia
- 4 Data Center
Route origin authorizations
A sample of 10 of this network’s 53 ROAs.
- 109.205.96.0/21 · max length /21
- 173.242.48.0/20 · max length /20
- 185.104.44.0/22 · max length /22
- 185.104.45.0/24 · max length /24
- 185.124.8.0/22 · max length /22
- 185.149.40.0/22 · max length /22
- 185.209.168.0/22 · max length /22
- 185.225.212.0/22 · max length /22
- 185.226.24.0/22 · max length /22
- 185.233.116.0/22 · max length /22
Upstreams
The networks that most often share an observed BGP path with AS200000.
Blast radius
- Announced IPv4 addresses
- 38,656
- Threat-listed addresses
- 27
- Threat density
- 0.0698 %
- Routed prefixes
- 31
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 9 of this network’s 9 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- WNET - WNET TELECOM USA Corp. · AS1820
- UARNET-AS - LLC EKSINTECH · AS3255
- Datagroup - PRIVATE JOINT STOCK COMPANY "DATAGROUP" · AS3326
- HURRICANE - Hurricane Electric LLC · AS6939
- RETN-AS - RETN Limited · AS9002
- ITS-UA - PRIVATE JOINT STOCK COMPANY "DATAGROUP" · AS13249
- IXP-1-IX-EU - A-Systems Sp. z o.o. · AS50263
- HOSTING-UKRAINE-2 - Hosting Ukraine LTD · AS200525
Reputation
14.9reputation score (NEUTRAL)
AS200000 (Ukraine-AS - Hosting Ukraine LTD, UA) has a reputation score of 60.3 (NEUTRAL).
- Threat density
- 56.5/100
- Graph metrics
- 65.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
- Hosting Ukraine LTD
- RIR
- RIPE
- Registered
- Thu, 07 Nov 2013 07:35:15 GMT
- Abuse contact
- network@abuse.team
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS200000 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.