Network · data from 2026-11-12

AS43885 INSTAL MATEL

Registry name: imatel INSTAL MATEL SL, ES · PeeringDB

17IPv4 routes 82.4% RPKI valid · 100.0% with a route object

2IPv6 routes 50.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

4No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS43885, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS43885, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


45.13.210.0/24	No ROA	RIR databaseRIPE	671 100%	68
46.232.171.0/24	No ROA	RIR databaseRIPE	671 100%	68
195.93.184.0/24	No ROA	RIR databaseRIPE	671 100%	68
2a12:d840:aa::/48	No ROA	RIR databaseRIPE	634 100%	69
31.210.144.0/22	Valid	RIR databaseRIPE	671 100%	68
37.143.120.0/21	Valid	RIR databaseRIPE	671 100%	68
46.232.174.0/24	Valid	RIR databaseRIPE	671 100%	68
46.232.175.0/24	Valid	RIR databaseRIPE	671 100%	68
91.200.116.0/22	Valid	RIR databaseRIPE	671 100%	68
109.70.235.0/24	Valid	RIR databaseRIPE	671 100%	68
185.60.40.0/22	Valid	RIR databaseRIPE	671 100%	68
185.112.79.0/24	Valid	RIR databaseRIPE	671 100%	68
185.211.196.0/22	Valid	RIR databaseRIPE	671 100%	68
185.213.196.0/22	Valid	RIR databaseRIPE	671 100%	68
185.247.124.0/24	Valid	RIR databaseRIPE	671 100%	68
188.212.36.0/24	Valid	RIR databaseRIPE	671 100%	68
188.215.84.0/24	Valid	RIR databaseRIPE	671 100%	68
193.162.14.0/24	Valid	RIR databaseRIPE	671 100%	68
2a10:ce00::/29	Valid	RIR databaseRIPE	633 100%	69

AS-SET

AS43885's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 5 are in fix.csv.

ROA: none4
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	45.13.210.0/24	No ROA covers it. Add a ROA for AS43885, maxLength 24.	671 of 673
ROA: none	46.232.171.0/24	No ROA covers it. Add a ROA for AS43885, maxLength 24.	671 of 673
ROA: none	195.93.184.0/24	No ROA covers it. Add a ROA for AS43885, maxLength 24.	671 of 673
ROA: none	2a12:d840:aa::/48	No ROA covers it. Add a ROA for AS43885, maxLength 48.	634 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

45.13.210.0/24

No ROA covers it. Add a ROA for AS43885, maxLength 24.

671 of 673

ROA: none

46.232.171.0/24

No ROA covers it. Add a ROA for AS43885, maxLength 24.

671 of 673

ROA: none

195.93.184.0/24

No ROA covers it. Add a ROA for AS43885, maxLength 24.

671 of 673

ROA: none

2a12:d840:aa::/48

No ROA covers it. Add a ROA for AS43885, maxLength 48.

634 of 636

Route objects not announced

Route objects with origin AS43885 whose prefix no peer sees AS43885 announce. Many are kept on purpose (backup routes, space announced only in some places).


2a02:7160::/32	RIPE	No ROA

2a02:7160::/32

RIPE

No ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.