Data as of Nov 19, 2026

51.162.176.0/21

1 residential-proxy exit · 30 days

Equinix (EMEA) Acquisition Enterprises B.V. · space held by Equinix (Services) Limited

Announcement
this exact prefix
No RPKI
Announced by
Type
Hosting

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 20, 2026 – Nov 18, 2026

Exits seen per day

3 observations

Proxy providers listing exits

  • Byteful

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
51.162.182.0/24
since May 2023
AS15830HostingEquinix (Services) Limited
51.162.183.0/24
since Feb 2026
AS15830HostingEquinix (Services) Limited

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
51.162.128.0 - 51.163.159.25573,728EQUINIXEquinix (Services) Limited (ORG-IA69-RIPE) · GBLEGACYNov 14, 2019smc@equinix.com
└ 51.162.128.0/1732,768EQUINIX-51-162-128-0-17Equinix (Services) Limited (ORG-IA69-RIPE) · GBLEGACYApr 12, 2018smc@equinix.com
└ 51.162.128.0/1816,384EQUINIX-51-162-128-0-18Equinix (Netherlands) Enterprises BV (ORG-EEB6-RIPE) · NLLEGACYFeb 10, 2021smc@equinix.com
└ 51.162.176.0/212,048EQUINIX-MBEquinix (Netherlands) Enterprises BV (ORG-EEB6-RIPE) · NLLEGACYSep 25, 2023smc@equinix.com
└ 51.162.176.44/304Digicert_Security_India_Private_LimitedunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.176.112/304Microcurve_Online_Private_LimitedEquinix Customer - Microcurve Online Private LimitedLEGACYAug 4, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.176.136/304Microcurve_Online_Private_LimitedEquinix Customer - Microcurve Online Private LimitedLEGACYAug 4, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.176.188/304Velrush_Business_Networks_Pvt_LtdunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.176.192/304Cisco_Systems_India_Private_Limited_UmbrellaunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.176.208/298Saab_India_Technologies_Private_LimitedunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.176.224/298Infosys_Limited_Siemens_AGunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.177.20/304Chevron_Global_Technology_and_Services_Private_LimitedunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.177.68/304Chevron_Global_Technology_and_Services_Private_LimitedunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.177.208/298Equinix_IndiaunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.177.216/298Cisco_Systems_India_Private_Limited_UmbrellaunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.177.224 - 51.162.177.2329Equinix_IndiaunknownLEGACYJul 23, 2026smc@equinix.com
via EQUINIX-MB
└ 51.162.179.224/2816Xonware_Technologies_Pvt_LtdEquinix Customer - Xonware Technologies Pvt LtdLEGACYOct 14, 2026smc@equinix.com
via EQUINIX-MB

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2022
Current origin since
May 2022 · 4.5 yr
Origin networks
1