Data as of Nov 13, 2026

185.63.128.0/22

No anonymizer space · no proxy exits in 30 days

Proact IT UK Limited · space held by Proact Deutschland GmbH

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

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
185.63.128.0/221,024DE-PROACT-20140710Proact Deutschland GmbH (ORG-PDG9-RIPE) · DEALLOCATED PAOct 21, 2025abuse@proact.de
└ 185.63.128.0/24256CLOUD-ACCESSunknownASSIGNED PAMay 10, 2018abuse@proact.de
via DE-PROACT-20140710
└ 185.63.129.0/25128CLOUD2-ACCESSunknownASSIGNED PAJan 8, 2020abuse@proact.de
via DE-PROACT-20140710
└ 185.63.129.128/2816CLOUD3-ACCESSunknownASSIGNED PAJan 8, 2020abuse@proact.de
via DE-PROACT-20140710
└ 185.63.129.144/298CLOUD4-ACCESSunknownASSIGNED PAJan 8, 2020abuse@proact.de
via DE-PROACT-20140710
└ 185.63.129.152/298PROXMOX-ACCESSunknownASSIGNED PAMay 10, 2018abuse@proact.de
via DE-PROACT-20140710
└ 185.63.129.160/298DENUE01-PROACTunknownASSIGNED PAJan 8, 2020abuse@proact.de
via DE-PROACT-20140710
└ 185.63.129.176/2816EE-IE-DMZ01-PROACTunknownASSIGNED PAJan 8, 2020abuse@proact.de
via DE-PROACT-20140710
└ 185.63.129.192/2664PROXMOX-ACCESSunknownASSIGNED PAMay 10, 2018abuse@proact.de
via DE-PROACT-20140710
└ 185.63.130.0/24256OPENSTACK-ACCESSunknownASSIGNED PAMay 10, 2018abuse@proact.de
via DE-PROACT-20140710
└ 185.63.131.2 - 185.63.131.87SCHLETTER01unknownASSIGNED PAApr 10, 2025abuse@proact.de
via DE-PROACT-20140710
└ 185.63.131.128/2664ITSA-LAB-ACCESSunknownASSIGNED PAMay 10, 2018abuse@proact.de
via DE-PROACT-20140710
└ 185.63.131.192/304ITSA-LAB-ACCESSunknownASSIGNED PAMay 10, 2018abuse@proact.de
via DE-PROACT-20140710
└ 185.63.131.227/321SCHLETTER02unknownASSIGNED PAApr 10, 2025abuse@proact.de
via DE-PROACT-20140710
└ 185.63.131.240/2816Z-BAU-ACCESSunknownASSIGNED PAJun 6, 2016abuse@proact.de
via DE-PROACT-20140710

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
Rotating
First seen
Jul 2014
Current origin since
Jul 2023 · 3.3 yr
Origin networks
2
Last change of origin
Jul 2023
Recorded history

History

Handoffs
1