Autonomous System
AS13000
Last fetched
AS13000 is operated by LEON-AS - Leon Sp. z o.o., registered in PL, and announces 42 prefixes to 13 BGP neighbours. AS13000 has a reputation score of 9.5 (REPUTABLE); 7 of its 51,456 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 42
- BGP neighbours
- 13
- RPKI ROAs
- 20
- MOAS conflicts
- 0
- CAIDA AS-rank
- 2,933
- Customer-cone ASNs
- 9
- Facilities
- 72
- Internet exchanges
- 5
- Customer degree
- 7
- Peer degree
- 116
- Provider degree
- 5
- 62.182.224.0/21
- 87.101.64.0/22
- 87.101.68.0/22
- 87.101.64.0/20
- 87.101.72.0/22
- 87.101.76.0/22
- 87.239.192.0/21
- 89.200.224.0/22
- 89.200.224.0/21
- 89.200.228.0/22
- 91.195.134.0/23
- 91.195.158.0/23
- 91.195.190.0/23
- 91.200.24.0/22
- 91.207.64.0/23
- 91.208.247.0/24
- 91.214.24.0/22
- 185.191.246.0/24
- 188.137.2.0/24
- 188.137.28.0/22
- 188.137.32.0/22
- 188.137.36.0/22
- 188.137.40.0/22
- 188.137.44.0/22
- 188.137.48.0/22
Infrastructure presence
Internet exchanges (5 total)
Facilities (72 total)
- NIKHEF Amsterdam
- Equinix AM7 - Amsterdam, Kuiperberweg
- Global Switch Amsterdam
- Equinix FR5 - Frankfurt, KleyerStrasse
- Digital Realty AMS17 - Amsterdam
- Digital Realty Frankfurt FRA1-27
- ITENOS Frankfurt (FRA1)
- Digital Realty AMS3/5/7/8/10 - Amsterdam
- Equinix FR7 - Frankfurt, Gutleutstrasse
- Telehouse - Frankfurt
- Digital Realty AMS9 - Amsterdam
- Digital Realty Frankfurt FRA28 (Closed)
- NTT Frankfurt 1 Data Center (FRA1)
- NewColo Frankfurt
- Iron Mountain Data Center - Amsterdam (AMS-1)
- Equinix AM1/AM2 - Amsterdam, Luttenbergweg
- LIM Warsaw
- Equinix FR2 - Frankfurt, North
- Equinix WA1 - Warsaw, Centrum LIM
- Equinix FR4 - Frankfurt, West
- Global Switch Frankfurt
- NewTelco Frankfurt
- Smartdc Rotterdam
- ATMAN Data Center Katowice-1 (KTW-1, Altus)
- NorthC Amsterdam 1
Route origin authorizations
A sample of 10 of this network’s 20 ROAs.
- 188.137.0.0/17 · max length /24
- 193.150.36.0/23 · max length /23
- 193.34.112.0/22 · max length /22
- 193.93.92.0/22 · max length /24
- 195.3.200.0/22 · max length /22
- 195.3.203.0/24 · max length /24
- 195.66.73.0/24 · max length /24
- 2a02:c40::/32 · max length /48
- 62.182.224.0/21 · max length /21
- 87.101.64.0/20 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS13000.
Blast radius
- Announced IPv4 addresses
- 51,456
- Threat-listed addresses
- 7
- Threat density
- 0.0136 %
- Routed prefixes
- 39
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 13 of this network’s 13 BGP neighbours.
- INTERDOTLINK - Inter.link GmbH · AS5405
- TPNET - Orange Polska Spolka Akcyjna · AS5617
- HURRICANE - Hurricane Electric LLC · AS6939
- LEON-AS2 - Leon Sp. z o.o. · AS12642
- SILWEB-AS-COM - Silesian University of Technology, Computer Centre · AS15744
- MEER-AS - meerfarbig GmbH & Co. KG · AS34549
- PGG-SA - Polska Grupa Gornicza S.A. · AS39255
- SPINE - Leon Sp. z o.o. · AS39412
- ERTEL-AS - Leon Sp. z o.o. · AS47129
- TKSWF-AS - Stadtwerke Feldkirch · AS48362
- LEON-GLOBAL - LEON-GLOBAL · AS49001
- JESTPRO - Marek Wajdzik · AS198469
- INGISP-AS - ING Hubs B.V. · AS202037
Reputation
9.5reputation score (REPUTABLE)
AS13000 (LEON-AS - Leon Sp. z o.o., PL) has a reputation score of 71.6 (REPUTABLE).
- Threat density
- 71.0/100
- Graph metrics
- 90.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
- Leon Sp. z o.o.
- RIR
- RIPE
- Registered
- Thu, 08 Dec 2005 09:54:41 GMT
- Abuse contact
- abuse@leon.pl
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS13000 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.