AS50187 BaikalWestCom Ltd 🇷🇺 RU
Announcing 26 prefixes, seen at the RIS collectors.
IPv4 prefixes
25
8,960 (35 × /24)
IPv6 prefixes
1
1 × /32
Upstreams
7
transit providers observed
Peers
2
settlement-free adjacencies
Downstreams
7
transit customers observed
Customer cone
6
ASes reachable through it
Registry and operator data
- AS number
- AS50187
- Name
- BaikalWestCom Ltd
- Organisation
- BWC
- Country
- 🇷🇺 RU
- RIR
- RIPENCC
- Allocated
- 2009-11-26
- Traffic levels
- 200-300Gbps
- Scope
- Regional
- Peering policy
- Open
- IRR as-set
- AS-BWC
- Website
- http://newbwc.ru
- PeeringDB
- net/42557
RPKI coverage of this AS
Its own announcements, validated against the current ROA set
Upstreams
Networks seen providing transit to this one
| Network | Country | Cone | IPv4 prefixes | Paths | Source |
|---|---|---|---|---|---|
| AS1299 Arelion (fka. Telia Carrier) | 🇸🇪 SE | 68,864 | 132 | 162 | CAIDA |
| AS20485 TransTeleCom JSC | 🇷🇺 RU | 28,176 | 85 | 242 | CAIDA |
| AS12389 Rostelecom PJSC | 🇷🇺 RU | 26,592 | 3,276 | 582 | CAIDA |
| AS9049 JSC "ER-Telecom Holding" | 🇷🇺 RU | 24,638 | 40 | 3 | CAIDA |
| AS3216 Vimpelcom PJSC | 🇷🇺 RU | 24,420 | 590 | 114 | CAIDA |
| AS20764 CJSC RASCOM | 🇷🇺 RU | 23,353 | 8 | 203 | CAIDA |
| AS44267 EN+ TELECOM LLC | 🇷🇺 RU | 17 | 13 | 227 | CAIDA |
Peers
Adjacencies that look settlement-free rather than transit
| Network | Country | Cone | IPv4 prefixes | Paths | Source |
|---|---|---|---|---|---|
| AS24482 SG.GS | 🇸🇬 SG | 4,758 | 45 | 35 | CAIDA |
| AS49673 Truenetwork LLC | 🇷🇺 RU | 9 | 4 | 35 | CAIDA |
Downstreams
Networks this one appears to provide transit to
| Network | Country | Cone | IPv4 prefixes | Paths | Source |
|---|---|---|---|---|---|
| AS42897 BaikalWestCom Ltd | 🇷🇺 RU | 0 | 5 | 262 | CAIDA |
| AS56535 Alpari Ltd. | 🇷🇺 RU | 0 | 7 | 84 | CAIDA |
| AS211587 LLC "ASF" | 🇷🇺 RU | 0 | 1 | 42 | CAIDA |
| AS57629 LLC IVI.RU | 🇷🇺 RU | 0 | 9 | 35 | inferred |
| AS213480 StroyProektServis LLC | 🇷🇺 RU | 0 | 1 | 14 | CAIDA |
| AS44345 Mayak LLC | 🇷🇺 RU | 0 | 1 | 12 | CAIDA |
Relationships marked inferred come from where the two networks sit on the AS paths the collectors see, which is a guess and is wrong for some of them. The rest are stated by CAIDA's published inference over a much wider set of collectors.