Data as of Nov 22, 2026

220.227.64.0/21

1 residential-proxy exit · 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
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
1
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

1 observation

Proxy providers listing exits

  • IPFly

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
220.227.64.0/24
since Sep 2024
AS18101UnknownReliance Communications Limited
220.227.66.0/24
since Sep 2024
AS18101UnknownReliance Communications Limited
220.227.68.0/24
since Sep 2024
AS18101UnknownReliance Communications Limited
220.227.69.0/24
since Sep 2024
AS18101UnknownReliance Communications Limited
220.227.71.0/24
since Jun 2025
AS18101UnknownReliance 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