LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

185.32.32.0/22

No anonymizer space · no proxy exits in 30 days

CANCOM Managed Services GmbH

Announcement
this exact prefix
RPKI valid
Announced by
AS8469
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.32.32.0/221,024DE-PIRONET-20130731CANCOM Managed Services GmbH (ORG-PNA1-RIPE) · DEALLOCATED PAJul 31, 2013abuse@cancom-pironet.de
└ 185.32.32.0/2732aixigoAG-NET2aixigo AG - financial training, research and technologyASSIGNED PAJan 7, 2014abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.32.48/2816CENTERDEVICE-GMBH-NET2CenterDevice GmbHASSIGNED PASep 23, 2013abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.32.64/298GEVA-NETGEVA Business Solutions GmbHASSIGNED PAJun 27, 2014abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.32.72/298SeenMediaGmbH-NET2Seen Media GmbHASSIGNED PANov 5, 2013abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.32.113/321GEVA-NETGEVA Business Solutions GmbHASSIGNED PAOct 10, 2014abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.32.114/312Zentis-DCA-NETZentis GmbH & Co. KGASSIGNED PASep 11, 2014abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.32.116/304SYNAIX-NETSynaix IT GmbHASSIGNED PAOct 7, 2014abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.32.176/2816OZV-NETOZV GmbH & Co. KGASSIGNED PAJun 27, 2014abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.32.216/298NEXT-NET2Next Kraftwerke GmbHASSIGNED PASep 19, 2014abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.32.232/298JT-NETJT Touristik GmbHASSIGNED PAFeb 18, 2016abuse@cancom-pironet.de
via DE-PIRONET-20130731
└ 185.32.34.0/24256SYNAIX-OPENSTACK-ONEsynaix Gesellschaft fuer angewandte Informations-Technologien mbHASSIGNED PANov 4, 2013abuse@cancom-pironet.de
via DE-PIRONET-20130731

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Aug 2013
Current origin since
Aug 2021 · 5.3 yr
Origin networks
2
Last change of origin
Aug 2021
Recorded history

History

Handoffs
1