Skip to main content

AS50473

ECO-AS

=== UPLINKS START ===

Registry

Authoritative registration data

AS number
50473
Name
ECO-AS
Organisation
=== UPLINKS START ===
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

22

IPv6 prefixes

0

Total announced

22

Announced prefixes

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

Prefixes announced by AS50473
80.251.224.0/20 IPv4 /20 not checked
46.151.152.0/21 IPv4 /21 not checked
83.137.48.0/21 IPv4 /21 not checked
185.191.56.0/22 IPv4 /22 not checked
185.21.156.0/22 IPv4 /22 not checked
185.26.28.0/22 IPv4 /22 not checked
185.42.124.0/22 IPv4 /22 not checked
185.61.76.0/22 IPv4 /22 not checked
194.36.196.0/22 IPv4 /22 not checked
91.214.240.0/22 IPv4 /22 not checked
94.141.244.0/22 IPv4 /22 not checked
94.141.252.0/22 IPv4 /22 not checked
185.42.124.0/23 IPv4 /23 not checked
185.42.126.0/23 IPv4 /23 not checked
188.64.166.0/23 IPv4 /23 not checked
185.21.159.0/24 IPv4 /24 not checked
188.64.165.0/24 IPv4 /24 not checked
193.105.59.0/24 IPv4 /24 not checked
194.36.197.0/24 IPv4 /24 not checked
194.36.199.0/24 IPv4 /24 not checked
195.216.241.0/24 IPv4 /24 not checked
46.151.155.0/24 IPv4 /24 not checked

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 AS50473
Address families
Eurasia Peering IX: Peering LAN 20,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 20,000 Mbps IPv4
PITER-IX Frankfurt 30,000 Mbps IPv4
PITER-IX Helsinki 30,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 30,000 Mbps IPv4
PITER-IX Riga: RIX_PEERING_VLAN 30,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 30,000 Mbps IPv4
PITER-IX Tallinn: TLL_PEERING VLAN 30,000 Mbps IPv4

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 AS50473 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

17 networks seen before AS50473 in AS paths

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS50473 in AS paths

Observed downstreams
Families
AS35377 TRN-TELECOM-AS 12 52
v4
AS31626 ZVITELECOM-AS 5 21
v4
AS51596 RUSTEKO-AS 6 18
v4

No rows match “”.

Showing – of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS41722 MIRAN-AS 5 28
v4
AS49544 i3Dnet 1 28
v4
AS36236 NETACTUATE 2 24
v4
AS49673 TRUENETWORK 2 23
v4
AS37721 ORG-VTS1-AFRINIC 2 19
v4
AS205112 PHILUNET 1 19
v4
AS28910 INTAL-ASN 3 7
v4
AS199524 GCORE 1 5
v4

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.