Data as of Nov 16, 2026

5.172.198.0/24

No anonymizer space · no proxy exits in 30 days

Lancom Ltd.

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.172.192.0/20
since Nov 2025
AS199081Hosting19Lancom Ltd.

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.172.192.0/204,096GR-LANCOM-20120731Lancom Ltd. (ORG-LL67-RIPE) · GRALLOCATED PAJul 31, 2012abuse@lancom.gr
└ 5.172.198.0/24256Customers-Cloud4Cloud-NetSUB-ALLOCATED PAJul 3, 2015abuse@lancom.gr
via GR-LANCOM-20120731
└ 5.172.198.0/2732Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via Customers-Cloud4
└ 5.172.198.33 - 5.172.198.5422Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via Customers-Cloud4
└ 5.172.198.56 - 5.172.198.8328Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via Customers-Cloud4
└ 5.172.198.84/321FOUR-GR_NET-LAN-THESS4gr.networks cloud ThessalonikiASSIGNED PAJul 3, 2015abuse@lancom.gr
via Customers-Cloud4
└ 5.172.198.119/321TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via Customers-Cloud4
└ 5.172.198.234 - 5.172.198.2385TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via Customers-Cloud4

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jun 2013
Current origin since
Jun 2013 · 13 yr
Origin networks
1