Data as of Nov 21, 2026

185.70.130.0/23

14 residential-proxy exits · 30 days

Trinity Ltd

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

Residential-proxy exits

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

Exits seen per day

1.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.70.130.0/2418
185.70.131.0/2416

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FloppyData
  • GEEKPROXY_TURBO
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PrivateProxy
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
185.70.128.0/22
since Sep 2016
AS59815Unknown34
3 always on
Trinity Ltd

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
185.70.128.0/221,024RU-TRINITY-20140917Trinity Ltd (ORG-TL979-RIPE) · RUALLOCATED PAAug 27, 2026kompeatelecom@gmail.com
└ 185.70.130.0/23512RU-KOMPEATELECOMKompeatelecom LtdASSIGNED PAOct 10, 2014kompeatelecom@gmail.com
via RU-TRINITY-20140917

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
Apr 2017
Current origin since
Apr 2017 · 9.6 yr
Origin networks
1