Data as of Nov 19, 2026

220.227.40.0/22

2 residential-proxy exits · 30 days

Reliance Communications Ltd.DAKC MUMBAI · space held by Reliance Communications Limited

Announcement
RPKI valid
Announced by
Type
Unknown

Residential-proxy exits

Proxy exits
2
0.20% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
16
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

4 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
220.227.40.0/2401
220.227.41.0/2401

Proxy providers listing exits

  • BottingTools
  • Byteful
  • FastProxy
  • GSocks
  • Geonix
  • Infatica
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyRack
  • Shifter
  • Smartproxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
220.227.40.0/24
since Sep 2024
AS18101Unknown1Reliance Communications Limited
220.227.41.0/24
since Sep 2024
AS18101Unknown1Reliance Communications Limited

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
220.224.0.0/14262,144RCOMReliance Communications Limited (ORG-RCL5-AP) · INALLOCATED PORTABLE—Antiabuse.Support@rcom.co.in
└ 220.227.0.0/1665,536RCOM-STATIC-DIAunknownALLOCATED NON-PORTABLE—Antiabuse.Support@rcom.co.in
via RCOM

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 220.227.0.0/16

220.227.0.0/16

Routing history

Pattern
Stable
First seen
Sep 2005
Current origin since
Sep 2005 · 21 yr
Origin networks
1