Home Prefix Lookup188.210.216.0/22

188.210.216.0/22 - INETUM ES Inetum Espana, S.A (AS48846)

IPv4RIPE NCCallocatedAS48846INETUM-ES-AS Inetum Espana, S.A. RPKI Valid

CIDR

188.210.216.0/22

IP Version

IPv4

Addresses

Mask

/22 (255.255.252.0)

Country

🇪🇸 Spain

RIR

RIPE NCC

Status

allocated

Allocated

2009-05-08

Announced BGP Routes

1 of 1 route

RPKI:

IRR:

Swipe sideways to see all columns →

Prefix	Origin AS	RPKI	IRR	Last Seen
188.210.216.0/22	AS48846 INETUM-ES-AS Inetum Espana, S.A.	Valid	RIPE	2026-10-11

More-Specific Announcements

4 more-specific announcements

Prefix	Origin AS	RPKI	IRR	Last Seen
188.210.216.0/24	AS48846 INETUM-ES-AS Inetum Espana, S.A.	Valid	-	2026-10-11
188.210.217.0/24	AS48846 INETUM-ES-AS Inetum Espana, S.A.	Valid	-	2026-10-11
188.210.218.0/24	AS48846 INETUM-ES-AS Inetum Espana, S.A.	Valid	-	2026-10-11
188.210.219.0/24	AS48846 INETUM-ES-AS Inetum Espana, S.A.	Valid	-	2026-10-11

RPKI ROAs

Prefix	Origin	Max Length	Trust Anchor
188.210.216.0/22	AS48846	/24	ripe

IRR Route Objects

Origin	Registry	Maintainer	Modified
AS48846	RIPE	INETUM-ES-MNT	2020-12-15

More Specific Prefixes

Prefix	AS	Country	Status
188.210.216.0/24	AS48846	🇪🇸ES	assigned
188.210.217.0/24	AS48846	🇪🇸ES	assigned
188.210.218.0/24	AS48846	🇪🇸ES	assigned
188.210.219.0/24	AS48846	🇪🇸ES	assigned

Transfer History

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

188.210.216.0/22Transfer · 2017-03-02
inAsset Networks, S.L.
RIPE NCC
→
Informatica El Corte Ingles SA
RIPE NCC
188.210.216.0/22Transfer · 2014-09-24
Jump Management SRL
RIPE NCC
→
inAsset Networks, S.L.
RIPE NCC

Date	Resource	From	To	Type
2017-03-02	188.210.216.0/22	inAsset Networks, S.L. RIPE NCC	Informatica El Corte Ingles SA RIPE NCC	Transfer
2014-09-24	188.210.216.0/22	Jump Management SRL RIPE NCC	inAsset Networks, S.L. RIPE NCC	Transfer

Origin ASN

AS48846

INETUM-ES-AS Inetum Espana, S.A.

Related Prefixes

More prefixes of AS48846

All prefixes of AS48846 →

Geolocation

Country🇪🇸SpainES

Coordinates40.4637, -3.7492 ↗

Abuse Contact

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/188.210.216.0/22

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

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

External Links

RIPEstat