Data as of Nov 17, 2026

202.22.198.0/24

15 residential-proxy exits · 30 days

Access Telecom (BD) Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium
Proxy exits nearby

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Always-on exits
6
40% of its exits
Providers
50
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

30K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LUMIPROXY
  • LemonBright
  • Maskify
  • NSocks
  • NiuProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
202.22.198.0/23
since Sep 2026
AS17469Internet provider16
6 always on
Access Telecom (BD) Ltd
202.22.192.0/21
since Sep 2016
AS17469Internet provider39
7 always on
Access Telecom (BD) Ltd
202.22.192.0/20
since May 2005
AS17469Residential59
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.198.0/24256NET-202-22-198-0Dedicated Static Assignment (V198)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
Jun 2008
Current origin since
Aug 2023 · 3.2 yr
Origin networks
1