Home Prefix Lookup185.245.60.0/22

185.245.60.0/22 - BGP Prefix

IPv4RIPE NCCallocated RPKI Valid

CIDR

185.245.60.0/22

IP Version

IPv4

Addresses

Mask

/22 (255.255.252.0)

Country

🇩🇪 Germany

City

Koblenz (Metternich)

RIR

RIPE NCC

Status

allocated

Allocated

2018-02-07

Announced BGP Routes

0 of 0 routes

RPKI:

IRR:

Swipe sideways to see all columns →

Prefix	Origin AS	RPKI	IRR	Last Seen
This prefix is not announced as a whole. Parts of it are announced as more-specific prefixes, see below.

More-Specific Announcements

6 more-specific announcements

Prefix	Origin AS	RPKI	IRR	Last Seen
185.245.60.0/24	AS200303 LUMASERV LUMASERV GmbH	Valid	-	2026-10-12
185.245.61.0/24	AS44486 SYNLINQ Oliver Horscht trading as "SYNLINQ"	Valid	-	2026-10-12
185.245.62.0/24	AS197170 TECHTIES-AS TechTies Inc.	Valid	-	2026-10-12
185.245.62.0/24	AS209630 KREDIT-AS LLC VASH KREDIT BANK	Invalid	-	2026-10-12
185.245.63.0/24	AS197170 TECHTIES-AS TechTies Inc.	Valid	-	2026-10-12
185.245.63.0/24	AS209630 KREDIT-AS LLC VASH KREDIT BANK	Invalid	-	2026-10-12

IRR Route Objects

Origin	Registry	Maintainer	Modified
AS200303	RIPE	MNT-LUMASERV	2021-06-07

More Specific Prefixes

Prefix	AS	Country	Status
185.245.61.0/24	AS44486	🇩🇪DE	assigned
185.245.62.0/24	AS197170	🇪🇸ES	assigned
185.245.63.0/24	AS202673	🇳🇱NL	assigned

Transfer History

Registry transfers of 185.245.60.0/22, blocks inside it, or blocks containing it.

185.245.60.0/22Transfer · 2023-12-19
Jan Philipp Waldecker trading as LUMASERV Systems
RIPE NCC
→
LUMASERV GmbH
RIPE NCC
185.245.60.0/22Transfer · 2021-05-31
blocklink GmbH
RIPE NCC
→
Jan Philipp Waldecker trading as LUMASERV Systems
RIPE NCC

Date	Resource	From	To	Type
2023-12-19	185.245.60.0/22	Jan Philipp Waldecker trading as LUMASERV Systems RIPE NCC	LUMASERV GmbH RIPE NCC	Transfer
2021-05-31	185.245.60.0/22	blocklink GmbH RIPE NCC	Jan Philipp Waldecker trading as LUMASERV Systems RIPE NCC	Transfer

Geolocation

Country🇩🇪GermanyDE

RegionRheinland-Pfalz

CityKoblenz (Metternich)

Coordinates50.3625, 7.5604 ↗

Learn more

RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
RPKI validatorCheck ROA coverage for any prefix or ASN
What is BGP?How prefixes are announced and routed
More-specific prefixesGlossary: covering and more-specific routes
IPv4 transfers in the RIPE NCC regionWho bought and sold address space recently

API

Open

GEThttps://api.ipctl.io/v1/prefix/185.245.60.0/22

Returns prefix allocation, BGP routes, and more-specific subnets.

curl -s "https://api.ipctl.io/v1/prefix/185.245.60.0/22" | jq

External Links

RIPEstat