Data as of Nov 18, 2026

178.21.168.0/22

1 residential-proxy exit · 30 days

Lancom Ltd.

Announcement
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
2
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

2 observations

Proxy providers listing exits

  • KocerRoxy
  • LemonBright

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
178.21.168.0/24
since Sep 2013
AS199081Hosting1Lancom Ltd.
178.21.169.0/24
since Sep 2013
AS199081HostingLancom Ltd.
178.21.170.0/24
since Sep 2013
AS199081HostingLancom Ltd.
via Lancom Ltd.
178.21.171.0/24
since Sep 2013
AS199081HostingLancom Ltd.
via Lancom Ltd.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.21.168.0/212,048GR-LANCOM-20100318Lancom Ltd. (ORG-LL67-RIPE) · GRALLOCATED PAMar 18, 2010abuse@lancom.gr
└ 178.21.168.0/24256LANCOM_178_BLOCK1Infra-NetASSIGNED PAApr 2, 2012abuse@lancom.gr
via GR-LANCOM-20100318
└ 178.21.169.0/24256Cloud-CustomersCloud-NetASSIGNED PAAug 28, 2017abuse@lancom.gr
via GR-LANCOM-20100318
└ 178.21.170.0/24256GR-LANCOM-20140724Lancom Ltd. (ORG-LL67-RIPE) · GRSUB-ALLOCATED PAJul 24, 2014abuse@lancom.gr
└ 178.21.170.0 - 178.21.170.128129Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.170.129 - 178.21.170.255127Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.0/24256GR-LANCOM-20140724Lancom Ltd. (ORG-LL67-RIPE) · GRSUB-ALLOCATED PAJul 24, 2014abuse@lancom.gr
└ 178.21.171.0 - 178.21.171.4748Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.48/321FOUR-GR_NET-LAN-THESS4gr.networks cloud ThessalonikiASSIGNED PAOct 11, 2013abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.49 - 178.21.171.6012FOUR-GR_NET-LAN-THESS4gr.networks cloud ThessalonikiASSIGNED PAApr 2, 2012abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.61 - 178.21.171.699Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.70/321FOUR-GR_NET-LAN-THESS4gr.networks cloud ThessalonikiASSIGNED PAApr 2, 2012abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.71 - 178.21.171.8313Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.85 - 178.21.171.939Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.94/321FOUR-GR_NET-LAN-THESS4gr.networks cloud ThessalonikiASSIGNED PAJun 9, 2012abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.95 - 178.21.171.1006Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.102 - 178.21.171.11312Cloud-CustomersunknownASSIGNED PAAug 28, 2017abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.154/321Hosting-ARunknownASSIGNED PANov 3, 2022abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.192/321TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.195/321TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.198/321TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.205/321TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.215/321TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.218/321TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.225 - 178.21.171.2262TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.232/321TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.246/312TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724
└ 178.21.171.250/321TDSunknownASSIGNED PAOct 11, 2023abuse@lancom.gr
via GR-LANCOM-20140724

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 178.21.168.0/21

178.21.168.0/21

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Dec 2020 · 6.0 yr
Origin networks
2
Last change of origin
Apr 2013
Recorded history

History

Handoffs
1