Data as of Nov 17, 2026

5.183.144.0/22

54 residential-proxy exits · 30 days

BaikalWestCom Ltd

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
54
5.3% of its addresses · 30 days
Always-on exits
17
31% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
72
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

32K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.183.145.0/241534
5.183.146.0/2419
5.183.144.0/2414
5.183.147.0/2406

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GeekProxy
  • Geonode
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LOKIPROXY
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateByte
  • ProxiesVision
  • Proxio
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RolaProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
5.183.144.0/24
since Nov 2022
AS42897Residential4
1 always on
BaikalWestCom Ltd
5.183.145.0/24
since Nov 2022
AS42897Residential34
15 always on
BaikalWestCom Ltd
5.183.146.0/24
since Jul 2025
AS50187Residential9
1 always on
BaikalWestCom Ltd
5.183.147.0/24
since Jul 2025
AS50187Residential6BaikalWestCom Ltd

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.183.144.0/221,024RU-TELNET-20190410BaikalWestCom Ltd (ORG-TL574-RIPE) · RUALLOCATED PAApr 10, 2019tech@newbwc.ru
└ 5.183.144.0/24256RU-TELNET-5_183_144unknownASSIGNED PAApr 16, 2024tech@newbwc.ru
via RU-TELNET-20190410
└ 5.183.145.0/24256RU-TELNET-5_183_145unknownASSIGNED PAApr 16, 2024tech@newbwc.ru
via RU-TELNET-20190410
└ 5.183.146.0/24256RU-TELNET-5_183_146unknownASSIGNED PAApr 16, 2024tech@newbwc.ru
via RU-TELNET-20190410
└ 5.183.147.0/24256RU-TELNET-5_183_147unknownASSIGNED PAApr 16, 2024tech@newbwc.ru
via RU-TELNET-20190410

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2019
Current origin since
Mar 2025 · 1.7 yr
Origin networks
1