Data as of Nov 20, 2026

5.183.144.0/24

4 residential-proxy exits · 30 days

BaikalWestCom Ltd

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
40
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

219 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • ProxiesVision
  • Proxio
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.183.144.0/22
since Mar 2025
AS42897Residential53
16 always on
BaikalWestCom 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

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2022
Current origin since
Nov 2022 · 4.0 yr
Origin networks
1