Autonomous System
AS13172
Last fetched
AS13172 is operated by ESO - Electroenergien Sistemen Operator EAD, registered in BG, and announces 9 prefixes to 3 BGP neighbours. AS13172 has a reputation score of 13.1 (NEUTRAL); 0 of its 1,536 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 9
- BGP neighbours
- 3
- RPKI ROAs
- 9
- MOAS conflicts
- 0
- CAIDA AS-rank
- 30,354
- Customer-cone ASNs
- 1
- Facilities
- 18
- Internet exchanges
- 2
- Customer degree
- 0
- Peer degree
- 17
- Provider degree
- 3
Infrastructure presence
Internet exchanges (2 total)
Facilities (18 total)
- Equinix FR5 - Frankfurt, KleyerStrasse
- NXDATA-1 Bucharest (BUH1)
- Sofia Data Center (SDC)
- TELEPOINT Sofia Centre
- iNES Datacenter Bucharest
- NXDATA-2 Bucharest (BUH2)
- Voxility IR1 Bucharest
- Equinix SO1 - Sofia
- M247 Europe Bucharest
- Teletrans Datacenter
- Evolink Data Center Sofia 2
- Evolink Data Center Sofia 1
- TELEPOINT Sofia East
- S3 Company Ltd.
- Equinix SO2 - Sofia
- efectRO DC1
- Radiocom
- Timisoara 1
Route origin authorizations
A sample of 9 of this network’s 9 ROAs.
- 185.108.188.0/24 · max length /24
- 185.108.191.0/24 · max length /24
- 195.225.127.0/24 · max length /24
- 2a03:d180::/32 · max length /32
- 2a03:d180:fffe::/48 · max length /48
- 2a03:d180:ffff::/48 · max length /48
- 91.211.232.0/24 · max length /24
- 91.211.234.0/24 · max length /24
- 91.211.235.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS13172.
Blast radius
- Announced IPv4 addresses
- 1,536
- Threat-listed addresses
- 0
- Threat density
- 0.0000 %
- Routed prefixes
- 6
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 3 of this network’s 3 BGP neighbours.
Reputation
13.1reputation score (NEUTRAL)
AS13172 (ESO - Electroenergien Sistemen Operator EAD, BG) has a reputation score of 63.8 (NEUTRAL).
- Threat density
- 73.7/100
- Graph metrics
- 55.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
- Electroenergien Sistemen Operator EAD
- RIR
- RIPE
- Registered
- Fri, 04 Feb 2005 13:49:16 GMT
- Abuse contact
- abuse@eso.bg
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS13172 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.