Data as of Nov 13, 2026
62.4.16.0/20
2 residential-proxy exits · 30 daysScaleway SAS
Residential-proxy exits
Proxy exits
2
0.05% of its addresses · 30 days
Oct 14, 2026 – Nov 12, 2026
Exits seen per day
3 observations
Registrations in this block
The registry's network records over this block, widest first, each under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 62.4.0.0/19 | 8,192 | FR-SCALEWAY-970513 | Scaleway SAS (ORG-TT1-RIPE) · FR | ALLOCATED PA | Apr 23, 2002 | abuse@ |
| └ 62.4.16.0/20 | 4,096 | SCALEWAY-DEDIBOX-IPFO | Scaleway (ORG-ONLI1-RIPE) | LIR-PARTITIONED PA | Jul 15, 2013 | abuse@ |
| └ 62.4.16.128/25 | 128 | IE-CUST-NRCONSEILS | IP range for NRCONSEILS | ASSIGNED PA | May 7, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.17.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.17.0-27 | ASSIGNED PA | Oct 9, 2015 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.17.32/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.17.32-27 | ASSIGNED PA | Sep 20, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.17.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.17.64-27 | ASSIGNED PA | Feb 12, 2019 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.17.96/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.17.96-27 | ASSIGNED PA | Jun 19, 2014 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.17.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.17.128-27 | ASSIGNED PA | Feb 19, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.17.160/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.17.160-27 | ASSIGNED PA | May 5, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.17.192/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.17.192-27 | ASSIGNED PA | Apr 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.18.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.18.0-27 | ASSIGNED PA | Oct 1, 2016 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.18.32/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.18.32-27 | ASSIGNED PA | Jan 10, 2014 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.18.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.18.64-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.18.96/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.18.96-27 | ASSIGNED PA | Mar 28, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.18.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.18.128-27 | ASSIGNED PA | Jun 9, 2015 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.19.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.19.0-27 | ASSIGNED PA | Oct 4, 2016 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.19.32/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.19.32-27 | ASSIGNED PA | Jul 15, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.19.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.19.64-27 | ASSIGNED PA | Jul 30, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.19.96/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.19.96-27 | ASSIGNED PA | Jul 15, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.19.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.19.128-27 | ASSIGNED PA | Nov 18, 2016 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.19.160/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.19.160-27 | ASSIGNED PA | May 4, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.19.192/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.19.192-27 | ASSIGNED PA | Jul 30, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.19.224/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.19.224-27 | ASSIGNED PA | Aug 13, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.20.0/26 | 64 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.20.0-26 | ASSIGNED PA | Jul 15, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.23.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.23.0-27 | ASSIGNED PA | Mar 1, 2016 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.23.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.23.64-27 | ASSIGNED PA | Aug 24, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.23.96/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.23.96-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.23.192/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.23.192-27 | ASSIGNED PA | Aug 24, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.24.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.24.0-27 | ASSIGNED PA | Feb 11, 2015 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.24.32/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.24.32-27 | ASSIGNED PA | Aug 23, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.24.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.24.64-27 | ASSIGNED PA | Jun 7, 2019 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.24.96/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.24.96-27 | ASSIGNED PA | Dec 27, 2015 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.24.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.24.128-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.24.160/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.24.160-27 | ASSIGNED PA | Nov 4, 2015 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.24.192/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.24.192-27 | ASSIGNED PA | Aug 24, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.24.224/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.24.224-27 | ASSIGNED PA | Sep 10, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.25.32/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.25.32-27 | ASSIGNED PA | Jun 23, 2016 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.25.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.25.64-27 | ASSIGNED PA | Sep 12, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.25.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.25.128-27 | ASSIGNED PA | Mar 28, 2019 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.25.160/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.25.160-27 | ASSIGNED PA | Apr 11, 2016 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.25.192/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.25.192-27 | ASSIGNED PA | Aug 24, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.25.224/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.25.224-27 | ASSIGNED PA | Sep 21, 2016 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.26.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.26.0-27 | ASSIGNED PA | Mar 22, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.26.32/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.26.32-27 | ASSIGNED PA | Apr 27, 2019 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.26.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.26.64-27 | ASSIGNED PA | Apr 15, 2014 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.26.96/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.26.96-27 | ASSIGNED PA | Feb 5, 2014 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.26.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.26.128-27 | ASSIGNED PA | Dec 23, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.26.192/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.26.192-27 | ASSIGNED PA | Aug 24, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.27.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.27.0-27 | ASSIGNED PA | Dec 4, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.27.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.27.128-27 | ASSIGNED PA | Sep 21, 2016 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.27.160/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.27.160-27 | ASSIGNED PA | Jan 15, 2019 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.27.192/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.27.192-27 | ASSIGNED PA | Aug 24, 2013 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.27.224/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.27.224-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.28.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.28.64-27 | ASSIGNED PA | Jan 18, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.28.96/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.28.96-27 | ASSIGNED PA | Jan 19, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.28.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.28.128-27 | ASSIGNED PA | Apr 21, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.28.160/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.28.160-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.28.224/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.28.224-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.29.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.29.0-27 | ASSIGNED PA | Apr 20, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.29.32/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.29.32-27 | ASSIGNED PA | Mar 1, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.29.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.29.64-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.29.160/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.29.160-27 | ASSIGNED PA | Dec 14, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.29.224/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.29.224-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.30.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.30.0-27 | ASSIGNED PA | Jan 19, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.30.32/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.30.32-27 | ASSIGNED PA | Dec 19, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.30.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.30.64-27 | ASSIGNED PA | Feb 16, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.30.96/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.30.96-27 | ASSIGNED PA | Jul 12, 2019 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.30.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.30.128-27 | ASSIGNED PA | Jul 9, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.30.192/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.30.192-27 | ASSIGNED PA | Aug 18, 2019 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.30.224/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.30.224-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.31.0/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.31.0-27 | ASSIGNED PA | Jan 19, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.31.32/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.31.32-27 | ASSIGNED PA | Feb 2, 2018 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.31.64/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.31.64-27 | ASSIGNED PA | Apr 5, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.31.96/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.31.96-27 | ASSIGNED PA | Mar 5, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.31.128/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.31.128-27 | ASSIGNED PA | Mar 4, 2019 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.31.160/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.31.160-27 | ASSIGNED PA | Nov 6, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.31.192/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.31.192-27 | ASSIGNED PA | Sep 24, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
| └ 62.4.31.224/27 | 32 | DEDIBOX-CUST-62_ | Dedibox customer IP range 62.4.31.224-27 | ASSIGNED PA | Jan 26, 2017 | abuse@ via SCALEWAY-DEDIBOX-IPFO |
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
Announced by
Covering announcement 62.4.0.0/19
- Prefix
- 62.4.0.0/19
- Announced by
- AS12876 Scaleway SAS
- Type
- Hosting
- RPKI
- RPKI valid
- Netname
- FR-SCALEWAY-970513
- Registrant
- Scaleway SAS
- RIR
- RIPE NCC
Origin network
AS12876
FR
- Name
- Scaleway SAS
- Type
- Hosting
- Registered
- Dec 20, 1999
- Domain
- scaleway.com
- Website
- www.scaleway.com
- Industry
- Hosting and Cloud Provider
- Spamhaus ASN-DROP
- not listed
- VPN servers
- 61
- Tor exits
- 7
Routing timeline
Who has announced 62.4.0.0/19
62.4.0.0/19
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- Aug 2013 · 13 yr
- Origin networks
- 2
- Last change of origin
- Aug 2013
Recorded history
History
- Handoffs
- 2
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 62.4.0.0/19 | AS12876 | /19 | RIPE | RPKI valid |
IRR
Route objects on 62.4.0.0/19
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12876 | RIPE | Scaleway | MNT-TISCALIFR | May 3, 2022 |
Whois
Registration for this announcement
- Range
- 62.
4. 0. 0/ 19 - Netname
- FR-SCALEWAY-970513
- Registrant
- Scaleway SAS
- Registrant country
- FR
- Organization
- Scaleway SAS (ORG-TT1-RIPE)
- Org country
- FR
- Type
- ALLOCATED PA
- Created
- Apr 23, 2002
- Updated
- May 26, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- FR
- Delegated
- May 13, 1997
- Status
- assigned
Report abuse
Abuse contact
- abuse@
proxad. net - Name
- Administrative Contact for ProXad
- Handle
- ACP23-RIPE