Autonomous System
AS199284
Last fetched
AS199284 is operated by encoLine - Thueringer Netkom GmbH, registered in DE, and announces 29 prefixes to 9 BGP neighbours. AS199284 has a reputation score of 11.1 (NEUTRAL); 12 of its 14,848 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 29
- BGP neighbours
- 9
- RPKI ROAs
- 12
- MOAS conflicts
- 0
- CAIDA AS-rank
- 6,489
- Customer-cone ASNs
- 3
- Facilities
- 39
- Internet exchanges
- 2
- Customer degree
- 1
- Peer degree
- 89
- Provider degree
- 5
- 5.102.160.0/21
- 5.102.166.0/24
- 5.102.167.0/24
- 91.137.16.0/22
- 91.137.20.0/22
- 91.137.16.0/20
- 91.137.24.0/22
- 91.137.28.0/22
- 91.137.48.0/22
- 91.137.56.0/22
- 91.137.56.0/21
- 91.137.60.0/22
- 178.19.224.0/22
- 178.19.228.0/22
- 178.19.224.0/20
- 178.19.232.0/22
- 178.19.236.0/22
- 185.97.180.0/23
- 185.97.180.0/22
- 185.97.182.0/23
- 217.17.206.0/23
- 2001:4bd8:52::/48
- 2a01:75c0::/36
- 2a01:75c0:1000::/36
- 2a01:75c0:2000::/36
Routing posture
- Hijack posture score
- 0.08
- Route leaks
- 4
Leak types observed: TYPE1_HAIRPIN_TURN, TYPE3_PROVIDER_TO_PEER.
Infrastructure presence
Internet exchanges (2 total)
Facilities (39 total)
- Equinix FR7 - Frankfurt, Gutleutstrasse
- Equinix FR5 - Frankfurt, KleyerStrasse
- Digital Realty Frankfurt FRA1-27
- ITENOS Frankfurt (FRA1)
- Telehouse - Frankfurt
- Digital Realty Frankfurt FRA28 (Closed)
- Speedbone Berlin
- NorthC Berlin
- NewColo Frankfurt
- NTT Frankfurt 1 Data Center (FRA1)
- euNetworks Colocation Berlin
- Equinix FR2 - Frankfurt, North
- DNS:NET Colo I Berlin
- CarrierColo Berlin Luetzow (I/P/B/ site B)
- NTT Berlin 1 Data Center (BER1)
- Carrierswitchraum Jena
- Equinix FR4 - Frankfurt, West
- Global Switch Frankfurt
- NewTelco Frankfurt
- CarrierColo Berlin Kitzing (I/P/B/ site K)
- 3U Rechenzentrum Berlin
- NTT Frankfurt 2 Data Center (FRA2)
- TelemaxX IPC4
- COLT DC Frankfurt
- AtlasEdge DC Berlin BER001
Route origin authorizations
A sample of 10 of this network’s 12 ROAs.
- 178.19.224.0/20 · max length /24
- 185.97.180.0/22 · max length /24
- 2001:4bd8:52::/48 · max length /48
- 217.17.206.0/23 · max length /23
- 2a01:75c0::/29 · max length /48
- 5.102.160.0/21 · max length /24
- 91.137.16.0/20 · max length /24
- 91.137.48.0/22 · max length /24
- 91.137.50.0/23 · max length /24
- 91.137.56.0/21 · max length /22
Upstreams
The networks that most often share an observed BGP path with AS199284.
Blast radius
- Announced IPv4 addresses
- 14,848
- Threat-listed addresses
- 12
- Threat density
- 0.0808 %
- Routed prefixes
- 21
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.
- INTERDOTLINK - Inter.link GmbH · AS5405
- HURRICANE - Hurricane Electric LLC · AS6939
- COLT - COLT Technology Services Group Limited · AS8220
- Etisalat-AS - EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC · AS8966
- IKS - IKS Service GmbH · AS15725
- CORE-BACKBONE - Core-Backbone GmbH · AS33891
- MEER-AS - meerfarbig GmbH & Co. KG · AS34549
- TKSWF-AS - Stadtwerke Feldkirch · AS48362
- TNETKOM-AS - Thueringer Netkom GmbH · AS196714
Reputation
11.1reputation score (NEUTRAL)
AS199284 (encoLine - Thueringer Netkom GmbH, DE) has a reputation score of 67.8 (NEUTRAL).
- Threat density
- 67.4/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
- Thueringer Netkom GmbH
- RIR
- RIPE
- Registered
- Tue, 26 Mar 2013 13:08:12 GMT
- Abuse contact
- abuse@netkom.de
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS199284 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.