Data as of Nov 16, 2026

87.255.21.0/24

4 residential-proxy exits · 30 days

Big Telecom JSC

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
32
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

921 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.255.16.0/21
since Jun 2009
AS35810Residential268
121 always on
Big Telecom JSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
87.255.0.0/198,192RU-BIGTELECOM-20051101Big Telecom JSC (ORG-BCJ2-RIPE) · RUALLOCATED PANov 1, 2005abuse@bigtelecom.ru
└ 87.255.16.0/212,048BIGTELECOMBig Telecom Closed JSCASSIGNED PAMay 29, 2009abuse@bigtelecom.ru
via RU-BIGTELECOM-20051101

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

87.255.20.0/22

Routing history

Pattern
Stable
First seen
Jul 2025
Current origin since
Jul 2025 · 1.3 yr
Origin networks
1