Network · data from 2026-11-12

AS8771 YUNET-AS YUnet International d.o.o.

Registry name: YUNET-AS YUnet International d.o.o., RS · not in PeeringDB

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

1IPv6 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 AS8771, seen from no peer

Announced routes

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


78.30.128.0/18	Valid	RIR databaseRIPE	673 100%	66
109.121.64.0/19	Valid	RIR databaseRIPE	673 100%	66
109.121.96.0/20	Valid	RIR databaseRIPE	673 100%	66
194.247.192.0/19	Valid	RIR databaseRIPE	673 100%	66
213.198.192.0/18	Valid	RIR databaseRIPE	673 100%	66
213.240.0.0/19	Valid	RIR databaseRIPE	673 100%	66
213.240.36.0/22	Valid	RIR databaseRIPE	673 100%	66
213.240.40.0/21	Valid	RIR databaseRIPE	673 100%	66
213.240.40.0/23	Valid	RIR databaseRIPE	673 100%	66
213.240.48.0/20	Valid	RIR databaseRIPE	673 100%	66
2a00:1108::/32	Valid	RIR databaseRIPE	635 100%	67

AS-SET

AS8771 isn't in PeeringDB, where networks name their 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 AS8771 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.