Network · data from 2026-11-12

AS62086 ViA Online

Registry name: VIADE VIA-ONLINE GmbH, DE · PeeringDB

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

6IPv6 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 AS62086, seen from no peer

Announced routes

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


185.48.104.0/22	Valid	RIR databaseRIPE	672 100%	66
185.48.104.0/24	Valid	RIR databaseRIPE	672 100%	66
185.48.105.0/24	Valid	RIR databaseRIPE	672 100%	66
185.48.106.0/24	Valid	RIR databaseRIPE	672 100%	66
185.48.107.0/24	Valid	RIR databaseRIPE	672 100%	66
2a01:9820::/32	Valid	RIR databaseRIPE	635 100%	69
2a01:9820:2::/48	Valid	RIR databaseRIPE	634 100%	67
2a01:9820:4::/48	Valid	RIR databaseRIPE	634 100%	67
2a01:9820:5::/48	Valid	RIR databaseRIPE	634 100%	67
2a01:9820:1::/48	Valid	RIR databaseRIPE	633 100%	67
2a01:9820:3::/48	Valid	RIR databaseRIPE	633 100%	67

AS-SET

AS62086'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 AS62086 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.