Skip to main content

AS50187

BWC

BaikalWestCom LLC

Registry

Authoritative registration data

AS number
50187
Name
BWC
Organisation
BaikalWestCom LLC
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

25

IPv6 prefixes

1

Total announced

26

Announced prefixes

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

Prefixes announced by AS50187
185.234.228.0/22 IPv4 /22 not checked
212.67.28.0/22 IPv4 /22 not checked
195.93.148.0/23 IPv4 /23 not checked
31.44.244.0/23 IPv4 /23 not checked
37.139.82.0/23 IPv4 /23 not checked
91.240.102.0/23 IPv4 /23 not checked
185.234.228.0/24 IPv4 /24 not checked
185.234.229.0/24 IPv4 /24 not checked
185.234.230.0/24 IPv4 /24 not checked
185.234.231.0/24 IPv4 /24 not checked
195.93.148.0/24 IPv4 /24 not checked
195.93.149.0/24 IPv4 /24 not checked
212.67.28.0/24 IPv4 /24 not checked
212.67.29.0/24 IPv4 /24 not checked
212.67.30.0/24 IPv4 /24 not checked
212.67.31.0/24 IPv4 /24 not checked
31.44.244.0/24 IPv4 /24 not checked
31.44.245.0/24 IPv4 /24 not checked
31.44.247.0/24 IPv4 /24 not checked
37.139.80.0/24 IPv4 /24 not checked
37.139.81.0/24 IPv4 /24 not checked
5.183.146.0/24 IPv4 /24 not checked
5.183.147.0/24 IPv4 /24 not checked
91.240.102.0/24 IPv4 /24 not checked
91.240.103.0/24 IPv4 /24 not checked
2a0e:26c0::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS50187 in AS paths

Observed upstreams
Families
AS12389 367 4,059
v4 v6
AS20764 RASCOM-AS 365 2,942
v4 v6
AS3216 SOVAM-AS 124 1,862
v4
AS20485 745 1,809
v4 v6
AS1299 122 1,724
v4 v6
AS44267 67 724
v4 v6
AS50384 22 83
v4 v6
AS9049 45 70
v4 v6

No rows match “”.

Showing of

Observed downstreams

7 networks seen after AS50187 in AS paths

Observed downstreams
Families
AS42897 585 2,218
v4 v6
AS56535 134 976
v4
AS57629 252 346
v6
AS211587 261 335
v4
AS213480 84 97
v4
AS44345 51 61
v4
AS44267 18 20
v4

No rows match “”.

Showing of

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS25091 5 111
v4
AS24482 SGGS-AS-AP 2 87
v4
AS36236 NETACTUATE 6 38
v4
AS41722 6 38
v4
AS28910 3 35
v4
AS41327 3 35
v4
AS49673 TRUENETWORK 3 35
v4
AS29049 4 31
v4
AS35598 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.