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

5.61.80.0/21

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
5.61.80.0/212,048DE-PIRONET-20120607CANCOM Managed Services GmbH (ORG-PNA1-RIPE) · DEALLOCATED PAJun 7, 2012abuse@cancom-pironet.de
└ 5.61.80.16/2816HITS-NETunknownASSIGNED PAOct 6, 2017abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.80.50/321MyEFA-HITS-NETunknownASSIGNED PAApr 10, 2017abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.81.0/2664SYNAIX-NETsynaix Gesellschaft fuer angewandte Informations-Technologien mbHASSIGNED PAAug 8, 2012abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.81.64/2732COMVELGmbH-NETCOMVEL GmbHASSIGNED PAApr 27, 2017abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.16/2816SYNAIX-CLOUDSynaix IT GmbHASSIGNED PAApr 9, 2015abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.32/298EKIR-NETEvangelische Kirche im RheinlandASSIGNED PAJul 27, 2016abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.40/304SYNAIX-H080-NETsynaix IT GmbHASSIGNED PAFeb 18, 2016abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.44/304SYNAIX-VOIP-NETsynaix IT GmbHASSIGNED PAFeb 18, 2016abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.57/321Trianel-NETTrianel GmbHASSIGNED PAMar 17, 2016abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.108/304NEXT-DCANext Kraftwerke GmbHASSIGNED PAApr 16, 2015abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.112/2816SYNAIX-NETsynaix IT GmbHASSIGNED PAJun 5, 2015abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.190/312SYNAIX-INFRA-VOIPsynaix Gesellschaft fuer angewandte Informations-Technologien mbHASSIGNED PAMar 6, 2015abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.216/298BG-TEST-NETunknownASSIGNED PAMar 16, 2017abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.224/2816EKIR-NETEvangelische Kirche im RheinlandASSIGNED PAMar 17, 2016abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.240/298EKIR2-NETEvangelische Kirche im RheinlandASSIGNED PAMar 17, 2016abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.82.248/298IDM-NETSynaix IT GmbHASSIGNED PAMar 17, 2016abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.83.48/2816INFORMGmbH-NETunknownASSIGNED PAMar 21, 2017abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.83.86/312SYNAIX-NETSynaix IT GmbHASSIGNED PAJul 2, 2014abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.83.88/304SYNAIX-NETSynaix IT GmbHASSIGNED PAJun 27, 2014abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.84.0/24256SYNAIX-DCA-SERVICES-DC1-NETsynaix Gesellschaft fuer angewandte Informations-Technologien mbHASSIGNED PAJul 26, 2013abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.85.0/24256SYNAIX-DCA-SERVICES-DC2-NETsynaix Gesellschaft fuer angewandte Informations-Technologien mbHASSIGNED PAJul 26, 2013abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.86.97 - 5.61.86.982ProService-GmbH-NETProService-GmbHASSIGNED PASep 23, 2019abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.86.99 - 5.61.86.1002ACCAMPO-GmbH-NETACCAMPO-GmbHASSIGNED PASep 23, 2019abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.86.101 - 5.61.86.1022EMOTO2-GmbH-NETEMOTO2-GmbHASSIGNED PASep 23, 2019abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.86.103 - 5.61.86.1042UEB-GmbH-NETUEB-GmbHASSIGNED PASep 23, 2019abuse@cancom-pironet.de
via DE-PIRONET-20120607
└ 5.61.87.0/24256SYNAIX-NETsynaix Gesellschaft fuer angewandte Informations-Technologien mbHASSIGNED PANov 19, 2012abuse@cancom-pironet.de
via DE-PIRONET-20120607

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 2012
Current origin since
Aug 2021 · 5.3 yr
Origin networks
2
Last change of origin
Aug 2021
Recorded history

History

Handoffs
1