Data as of Nov 15, 2026

5.172.206.0/24

5 residential-proxy exits · 30 days

Lancom Ltd.

Announcement

this exact prefix

RPKI valid

Announced by

AS199081

Type

Hosting

Risk

50 / 100 · Medium

Residential-proxy exits

Proxy exits

2.0% of its addresses · 30 days

Providers

selling exits here

Oct 16, 2026 – Nov 14, 2026

Exits seen per day

72 observations

Proxy providers listing exits

FastProxy
KocerRoxy
LemonBright
ThunderProxy
VitalExclusive

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
5.172.192.0/20 since Nov 2025	AS199081	Hosting	19	Lancom 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.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
5.172.192.0/20	4,096	GR-LANCOM-20120731	Lancom Ltd. (ORG-LL67-RIPE) · GR	ALLOCATED PA	Jul 31, 2012	abuse@lancom.gr
└ 5.172.206.0/24	256	Lancom-Block-5	ISP-Net	SUB-ALLOCATED PA	Nov 30, 2021	abuse@lancom.gr via GR-LANCOM-20120731
└ 5.172.206.80/28	16	ZR-LeasedLine	unknown	ASSIGNED PA	Nov 30, 2021	abuse@lancom.gr via Lancom-Block-5

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

Announcement Routing history RPKI & IRR Whois & abuse

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
5.172.206.0/24	AS199081	/24	RIPE	RPKI valid
5.172.204.0/22	AS199081	/22	RIPE	Too specific
5.172.192.0/20	AS199081	/20	RIPE	Too specific

IRR

Route objects on the exact prefix

Origin	Registry	Description	Maintainer	Modified
AS199081	RIPE		MNT-LANCOM1	Aug 29, 2016