Data as of Nov 12, 2026

87.255.8.0/22

40 residential-proxy exits · 30 days

Big Telecom JSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
40
3.9% of its addresses · 30 days
Always-on exits
5
13% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
76
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

9.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.255.8.0/24317
87.255.10.0/24113
87.255.9.0/2415
87.255.11.0/2405

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
87.255.8.0/24
since Oct 2006
AS35810Residential17
3 always on
Big Telecom JSC
via Big Telecom Closed JSC
87.255.9.0/24
since Oct 2006
AS35810Residential5
1 always on
Big Telecom JSC
via Big Telecom Closed JSC

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
87.255.0.0/198,192RU-BIGTELECOM-20051101Big Telecom JSC (ORG-BCJ2-RIPE) · RUALLOCATED PANov 1, 2005abuse@bigtelecom.ru
└ 87.255.8.0/221,024BIGTELECOMBig Telecom Closed JSCLIR-PARTITIONED PAOct 6, 2006abuse@bigtelecom.ru
via RU-BIGTELECOM-20051101
└ 87.255.8.0/24256BIGTELECOMBig Telecom Closed JSCASSIGNED PAOct 24, 2006abuse@bigtelecom.ru
via BIGTELECOM
└ 87.255.9.0/24256BIGTELECOMBig Telecom Closed JSCASSIGNED PAOct 24, 2006abuse@bigtelecom.ru
via BIGTELECOM
└ 87.255.10.0/23512BIGTELECOMBig Telecom Closed JSCASSIGNED PAFeb 12, 2008abuse@bigtelecom.ru
via BIGTELECOM

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
Jul 2008
Current origin since
Jul 2008 · 18 yr
Origin networks
1