Skip to main content

AS50923

METRO-SET-AS

Metroset Autonomous System

Registry

Authoritative registration data

AS number
50923
Name
METRO-SET-AS
Organisation
Metroset Autonomous System
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

16

IPv6 prefixes

1

Total announced

17

Announced prefixes

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

Prefixes announced by AS50923
178.208.224.0/19 IPv4 /19 RPKI valid
178.208.224.0/20 IPv4 /20 not checked
178.208.240.0/20 IPv4 /20 not checked
37.143.96.0/20 IPv4 /20 RPKI valid
5.53.16.0/20 IPv4 /20 not checked
37.143.104.0/21 IPv4 /21 RPKI valid
37.143.96.0/21 IPv4 /21 RPKI valid
37.60.16.0/21 IPv4 /21 RPKI valid
5.53.16.0/21 IPv4 /21 RPKI valid
5.53.24.0/21 IPv4 /21 not checked
185.3.68.0/22 IPv4 /22 RPKI valid
37.60.16.0/22 IPv4 /22 RPKI valid
37.60.20.0/22 IPv4 /22 not checked
185.3.68.0/23 IPv4 /23 RPKI valid
185.3.70.0/23 IPv4 /23 RPKI valid
37.143.97.0/24 IPv4 /24 RPKI valid
2a00:ae40::/32 IPv6 /32 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 AS50923
Address families
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4 · IPv6
GNM-IX 100,000 Mbps IPv4 · IPv6
Global-IX 10,000 Mbps IPv4 · IPv6
MSK-IX Ekaterinburg 40,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 40,000 Mbps IPv4 · IPv6
MSK-IX Novosibirsk 1,000 Mbps IPv4 · IPv6
Netnod Stockholm BLUE -- MTU1500: STH-B -- MTU1500 4,000 Mbps IPv4 · IPv6
Netnod Stockholm GREEN -- MTU1500: STH-A -- MTU1500 4,000 Mbps IPv4 · IPv6
OMSK-IX 10,000 Mbps IPv4
RED-IX 2,000 Mbps IPv4 · IPv6
SOLIX MTU1500 10,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 AS50923 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

31 networks seen before AS50923 in AS paths

No rows match “”.

Showing – of

Observed downstreams

7 networks seen after AS50923 in AS paths

Observed downstreams
Families
AS48873 proxi-com 326 2,909
v4
AS39735 RU-Permtelecom 284 1,711
v4
AS15493 RUSCOMP-AS 420 1,062
v4 v6
AS44627 LINKSU-AS 316 698
v4
AS57363 CDNvideo-AS 280 350
v4
AS202136 A-Siti-AS 155 340
v4 v6
AS207353 Ruform 7 9
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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