Data as of Nov 17, 2026

103.216.57.0/24

55 residential-proxy exits · 30 days

Triangle Services Limited. · space held by T-Network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
55
21% of its addresses · 30 days
Always-on exits
45
82% of its exits
Providers
51
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

216K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MangoProxy
  • Maskify
  • NSocks
  • Novada
  • Oxylabs
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RapidProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
103.216.56.0/23
since Nov 2025
AS45766Business65
45 always on
T-Network
via Corporate-Dedicated
103.216.56.0/22
since Nov 2018
AS45766Residential139
108 always on
T-Network

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
103.216.56.0/221,024TNETWORK-BDT-Network (ORG-TA13-AP) · BDALLOCATED PORTABLE—abuse@triangle.com.bd
└ 103.216.56.0/23512Triangle-Corporate-UserCorporate-DedicatedALLOCATED NON-PORTABLE—abuse@triangle.com.bd
└ 103.216.57.0/24256Triangle-Corporate-UserCorporate-DedicatedASSIGNED NON-PORTABLE—abuse@triangle.com.bd

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Aug 2016
Current origin since
Aug 2016 · 10 yr
Origin networks
1