Data as of Nov 20, 2026

188.65.168.0/21

1 residential-proxy exit · 30 days

IPGarde SAS

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

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 21, 2026 – Nov 19, 2026

Exits seen per day

1 observation

Proxy providers listing exits

  • AnyIP

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
188.65.168.0/212,048FR-IPGARDE-20090812IPGarde SAS (ORG-IA844-RIPE) · FRALLOCATED PAAug 12, 2009telco@ipgarde.com
└ 188.65.168.0/23512FR-IPGARDE-ISPIPGarde SASASSIGNED PAJan 13, 2010telco@ipgarde.com
via FR-IPGARDE-20090812
└ 188.65.170.0/24256FR-IPGARDE-BACKBONEIPGarde SASASSIGNED PANov 5, 2012telco@ipgarde.com
via FR-IPGARDE-20090812
└ 188.65.171.0/24256FR-IPGARDE-20110517IPGarde SASASSIGNED PAMay 17, 2011telco@ipgarde.com
via FR-IPGARDE-20090812
└ 188.65.172.0/221,024FR-IPGARDE-20110517IPGarde SASASSIGNED PAMay 17, 2011telco@ipgarde.com
via FR-IPGARDE-20090812

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
Mar 2010
Current origin since
Mar 2010 · 17 yr
Origin networks
1