Network · data from 2026-11-12

AS5533 VIA NET.WORKS Portugal

Registry name: CLARANET-PT Claranet Portugal S.A, PT · PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object

4IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

0Route objects not announced registered with origin AS5533, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS5533, 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.


77.91.200.0/21	Valid	RIR databaseRIPE	673 100%	67
80.172.0.0/16	Valid	RIR databaseRIPE	673 100%	67
188.93.224.0/21	Valid	RIR databaseRIPE	673 100%	67
193.227.238.0/23	Valid	RIR databaseRIPE	673 100%	67
194.62.240.0/22	Valid	RIR databaseRIPE	673 100%	67
195.35.66.0/24	Valid	RIR databaseRIPE	673 100%	67
195.72.136.0/22	Valid	RIR databaseRIPE	673 100%	67
185.146.92.0/22	Valid	RIR databaseRIPE	672 100%	67
195.22.0.0/19	Valid	RIR databaseRIPE	671 100%	67
2001:4cc0::/32	Valid	RIR databaseRIPE	635 100%	67
2a02:27e0::/32	Valid	RIR databaseRIPE	635 100%	67
2a03:73c0::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:4f40::/29	Valid	RIR databaseRIPE	634 100%	67

AS-SET

AS5533's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS5533 is announced.

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.