Data as of Nov 13, 2026

5.134.216.0/22

4 residential-proxy exits · 30 days

TrunkMobile JSC

Announcement
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
26
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

355 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.134.216.0/2402
5.134.217.0/2401
5.134.219.0/2401

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • BestProxy
  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • Datarama
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • IPFly
  • InfiniteProxies
  • NSocks
  • NextProxy
  • NovaProxy
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • ZENPROXY_PREMIUM

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.134.216.0/212,048RU-TRUNKMOBILE-20120711TrunkMobile JSC (ORG-TJ113-RIPE) · RUALLOCATED PAJan 26, 2026abuse@comfortel.pro
└ 5.134.216.0/24256WILANDNetwork for customersASSIGNED PAOct 30, 2012abuse@comfortel.pro
via RU-TRUNKMOBILE-20120711
└ 5.134.217.0/24256WILANDNetwork for customersASSIGNED PAMar 20, 2013abuse@comfortel.pro
via RU-TRUNKMOBILE-20120711
└ 5.134.218.0/24256WILANDNetwork for customersASSIGNED PAMar 20, 2013abuse@comfortel.pro
via RU-TRUNKMOBILE-20120711
└ 5.134.219.0/24256WILANDNetwork for customersASSIGNED PAApr 19, 2013abuse@comfortel.pro
via RU-TRUNKMOBILE-20120711

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 5.134.216.0/21

5.134.216.0/21

Routing history

Pattern
Stable
First seen
Nov 2012
Current origin since
Nov 2012 · 14 yr
Origin networks
1