Data as of Nov 11, 2026

210.4.68.0/24

6 residential-proxy exits · 30 days

BDCOM Online Limited

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
36
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

3.1K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • FlashProxy
  • FloppyData
  • Geonode
  • IPFly
  • IPPeak
  • InfiniteProxies
  • Kookey
  • NSocks
  • NiuProxy
  • Novada
  • Oxylabs
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • ZENPROXY_PREMIUM

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
210.4.64.0/204,096BDCOMBDCOM Online Limited (ORG-BOL2-AP) · BDALLOCATED PORTABLE—abuse@bdcom.com
└ 210.4.68.0/2664BDCOM-SylhetPOP-Local-LAN-IPBDCOM Sylhet branch local LAN IPASSIGNED NON-PORTABLE—abuse@bdcom.com
└ 210.4.68.64/2664BDCOM-SylhetPOP-Corporate-Client-DHCP-IPBDCOM Sylhet branch Corporate client DHCP IP PoolASSIGNED NON-PORTABLE—abuse@bdcom.com
└ 210.4.68.128/25128BDCOM-SylhetPOP-Broadband-Client-DHCP-PoolBDCOM Sylhet branch Broadband client DHCP IP PoolASSIGNED NON-PORTABLE—abuse@bdcom.com

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

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