Data as of Nov 13, 2026

87.255.6.0/24

12 residential-proxy exits · 30 days

Big Telecom JSC

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Always-on exits
3
25% of its exits
Providers
61
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

4.1K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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.4.0/221,024BIGTELECOMBig Telecom Closed JSCASSIGNED PAMay 7, 2006abuse@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

Who has announced 87.255.4.0/22

87.255.4.0/22

Routing history

Pattern
Stable
First seen
Jun 2006
Current origin since
Jun 2006 · 20 yr
Origin networks
1