bgpreport

Network · data from 2026-11-12

AS202616 Wien Energie Superschnell

Registry name: WE-FTTH-AS Wien Energie GmbH, AT · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS202616, seen from no peer

Announced routes

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

2a00:98c6::/31 No ROA RIR databaseRIPE 635 100% 69
194.0.72.0/23 Valid RIR databaseRIPE 673 100% 66
213.255.218.0/23 Valid RIR databaseRIPE 673 100% 66
217.194.146.0/24 Valid RIR databaseRIPE 673 100% 66
217.194.149.0/24 Valid RIR databaseRIPE 673 100% 66
217.194.154.0/23 Valid RIR databaseRIPE 673 100% 66
31.99.190.0/23 Valid RIR databaseRIPE 672 100% 66
195.69.173.0/24 Valid RIR databaseRIPE 672 100% 66
217.175.198.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS202616'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 3 are in fix.csv.

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a00:98c6::/31No ROA covers it. Add a ROA for AS202616, maxLength 31.635 of 636

Route objects not announced

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

2a00:98c6::/32RIPENo ROA
2a00:98c7::/32RIPENo 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.