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 not checked
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 not checked
5.53.16.0/20 IPv4 /20 not checked
37.143.104.0/21 IPv4 /21 not checked
37.143.96.0/21 IPv4 /21 not checked
37.60.16.0/21 IPv4 /21 not checked
5.53.16.0/21 IPv4 /21 not checked
5.53.24.0/21 IPv4 /21 not checked
185.3.68.0/22 IPv4 /22 not checked
37.60.16.0/22 IPv4 /22 not checked
37.60.20.0/22 IPv4 /22 not checked
185.3.68.0/23 IPv4 /23 not checked
185.3.70.0/23 IPv4 /23 not checked
37.143.97.0/24 IPv4 /24 not checked
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
AMS-IX 4,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 5,000 Mbps IPv4 · IPv6
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

27 networks seen before AS50923 in AS paths

Observed upstreams
Families
AS20485 989 3,377
v4 v6
AS31500 861 2,137
v4 v6
AS35598 448 1,446
v4
AS28917 606 1,427
v4 v6
AS1299 TWELVE99 223 1,080
v4 v6
AS174 COGENT-174 171 638
v4 v6
AS9049 102 389
v4
AS6939 HURRICANE 92 343
v4
AS25091 IP-Max 28 262
v4 v6
AS62255 100 245
v4
AS3216 SOVAM-AS 20 130
v4 v6
AS50304 24 84
v4 v6
AS47692 14 81
v4 v6
AS3303 SWISSCOM 20 66
v4 v6
AS41327 FIBERTELECOM-AS 14 51
v4 v6
AS56655 GIGAHOST 17 50
v4 v6
AS9198 17 49
v4 v6
AS49434 17 49
v4 v6
AS35280 F5 13 44
v4 v6
AS42295 TBISS-AS 9 37
v4
AS15958 10 30
v4
AS6663 7 27
v4 v6
AS5405 9 26
v4 v6
AS4455 7 24
v4 v6
AS60171 7 21
v4 v6
AS13194 1 1
v4
AS51028 1 1
v4

No rows match “”.

Showing of

Observed downstreams

8 networks seen after AS50923 in AS paths

Observed downstreams
Families
AS15493 1,062 3,219
v4 v6
AS48873 374 2,943
v4
AS39735 292 1,723
v4
AS204077 520 1,043
v4
AS44627 317 700
v4
AS202136 250 562
v4 v6
AS57363 291 352
v4
AS207353 Ruform 5 6
v4

No rows match “”.

Showing of

Uncertain adjacencies

30 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 7 217
v4 v6
AS8218 NEO-ASN 7 189
v4 v6
AS49544 i3Dnet 7 54
v4 v6
AS3170 18 52
v4 v6
AS36236 NETACTUATE 14 48
v4 v6
AS41722 13 47
v4 v6
AS42473 14 45
v4 v6
AS29049 15 43
v4
AS205206 10 35
v4
AS208972 11 31
v4
AS13004 10 30
v4
AS44901 10 30
v4
AS205112 PHILUNET 8 29
v4 v6
AS209823 8 29
v4 v6
AS200612 8 26
v4
AS37721 ORG-VTS1-AFRINIC 7 25
v4
AS42541 7 25
v4 v6
AS51185 MAINSTREAMING-AS 7 24
v4
AS199524 GCORE 7 24
v4
AS49673 TRUENETWORK 6 22
v4
AS15493 7 17
v4
AS48873 1 9
v4
AS39735 1 6
v4
AS28910 2 4
v6
AS202136 1 3
v4 v6
AS39351 ESAB-AS 2 2
v6
AS51519 Karabro 2 2
v6
AS44627 1 2
v4
AS204077 1 2
v4
AS57363 1 1
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.