Skip to main content

AS50254

sky-en

Sky Engineering LLC

Registry

Authoritative registration data

AS number
50254
Name
sky-en
Organisation
Sky Engineering LLC
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS50254
185.145.124.0/22 IPv4 /22 not checked
185.145.124.0/24 IPv4 /24 not checked
83.219.234.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 AS50254
Address families
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4 · IPv6
GNM-IX 10,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Tallinn: TLL_PEERING VLAN 10,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 AS50254 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

18 networks seen before AS50254 in AS paths

Observed upstreams
Families
AS35598 504 2,420
v4
AS3216 SOVAM-AS 285 1,017
v4
AS29076 172 835
v4
AS31500 266 823
v4
AS1299 TWELVE99 115 665
v4
AS8218 NEO-ASN 10 134
v4
AS47692 10 53
v4
AS25091 IP-Max 9 43
v4
AS6663 6 18
v4
AS15958 6 18
v4
AS42295 TBISS-AS 6 18
v4
AS62255 5 17
v4
AS50673 4 16
v4
AS9198 7 12
v4
AS60171 5 10
v4
AS137409 GSLNETWORKS-AS-AP 5 10
v4
AS199599 5 8
v4
AS14840 ASN14840 2 5
v4

No rows match “”.

Showing of

Observed downstreams

5 networks seen after AS50254 in AS paths

Observed downstreams
Families
AS31225 323 4,129
v4
AS44715 301 390
v4
AS62333 296 387
v4
AS57843 INTERLOGICA-LTD-AS 204 264
v4
AS211446 105 128
v4

No rows match “”.

Showing of

Uncertain adjacencies

20 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.