Data as of Nov 13, 2026

202.22.196.0/24

5 residential-proxy exits · 30 days

Access Telecom (BD) Ltd.

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
20
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

6 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • FloppyData
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonBright
  • MangoProxy
  • Novada
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Thordata
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
202.22.196.0/23
since Sep 2026
AS17469Internet provider22Access Telecom (BD) Ltd
202.22.192.0/21
since Sep 2016
AS17469Internet provider41
7 always on
Access Telecom (BD) Ltd
202.22.192.0/20
since May 2005
AS17469Residential60
7 always on
Access Telecom (BD) 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
202.22.192.0/204,096ACCESSTEL-BDAccess Telecom (BD) Ltd (ORG-ATL6-AP) · BDALLOCATED PORTABLE—abuse.report@accesstel.net
└ 202.22.196.0/24256NET-202-22-196-0Xstream Wireless DHCP Residential Service (V500)ASSIGNED NON-PORTABLE—abuse.report@accesstel.net
via ACCESSTEL-BD

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
Mar 2008
Current origin since
Oct 2023 · 3.1 yr
Origin networks
1