Data as of Nov 12, 2026

87.255.9.0/24

5 residential-proxy exits · 30 days

Big Telecom JSC

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
35
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

872 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Datarama
  • Evomi
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • Shifter
  • Smartproxy
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.255.8.0/22
since Jul 2008
AS35810Residential40
5 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.9.0/24256BIGTELECOMBig Telecom Closed JSCASSIGNED PAOct 24, 2006abuse@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

Covering aggregate above, the prefix's own history below

Summary

Routing history

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