bgpreport

Network · data from 2026-11-12

AS20792 VISTEC

Registry name: VISTEC-AS VISTEC Internet Service GmbH, DE · PeeringDB

4IPv4 routes 75.0% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No 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 AS20792, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20792, 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.87.189.0/24 No ROA RIR databaseRIPE 672 100% 66
2001:67c:d5c::/48 No ROA RIR databaseRIPE 635 100% 70
185.95.192.0/22 Valid RIR databaseRIPE 673 100% 66
212.237.228.0/24 Valid RIR databaseRIPE 673 100% 66
213.216.0.0/19 Valid RIR databaseRIPE 673 100% 66
2a02:13c0::/32 Valid RIR databaseRIPE 635 100% 70
2a0f:fa42::/32 Valid RIR databaseRIPE 635 100% 68

AS-SET

AS20792'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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none77.87.189.0/24No ROA covers it. Add a ROA for AS20792, maxLength 24.672 of 673
ROA: none2001:67c:d5c::/48No ROA covers it. Add a ROA for AS20792, maxLength 48.635 of 636

Route objects not announced

Every route object with origin AS20792 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.