Skip to main content

AS13172

ESO

Electroenergien Sistemen Operator EAD

Registry

Authoritative registration data

AS number
13172
Name
ESO
Organisation
Electroenergien Sistemen Operator EAD
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

3

Total announced

9

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS13172
185.108.188.0/24 IPv4 /24 RPKI valid
185.108.191.0/24 IPv4 /24 RPKI valid
195.225.127.0/24 IPv4 /24 RPKI valid
91.211.232.0/24 IPv4 /24 not checked
91.211.234.0/24 IPv4 /24 RPKI valid
91.211.235.0/24 IPv4 /24 not checked
2a03:d180::/32 IPv6 /32 RPKI valid
2a03:d180:fffe::/48 IPv6 /48 not checked
2a03:d180:ffff::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS13172
Address families
BIX.BG: Main 4,000 Mbps IPv4 · IPv6
InterLAN-IX: InterLAN Peering Network 20,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS13172 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

16 networks seen before AS13172 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS13172 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

14 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.