LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

87.255.18.0/23

9 residential-proxy exits · 30 days

Big Telecom JSC

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

Residential-proxy exits

Proxy exits
9
1.8% of its addresses · 30 days
Always-on exits
2
22% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.255.19.0/2427
87.255.18.0/2402

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.255.16.0/21
since Jun 2009
AS35810Residential265
126 always on
Big Telecom 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.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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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