bgpreport

Network · data from 2026-11-12

AS6764 Perftech

Registry name: PERFTECH-SLOVENIA-AS PERFTECH, podjetje za proizvodnjo in uvajanje novih tehnologij, d.o.o., SI · PeeringDB

6IPv4 routes 0.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
7No 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 AS6764, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS6764, 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.
193.28.14.0/24 No ROA RIR databaseRIPE 673 100% 66
193.28.43.0/24 No ROA RIR databaseRIPE 673 100% 66
193.28.51.0/24 No ROA RIR databaseRIPE 673 100% 66
193.28.54.0/24 No ROA RIR databaseRIPE 673 100% 66
195.246.0.0/19 No ROA RIR databaseRIPE 673 100% 66
212.118.64.0/19 No ROA RIR databaseRIPE 673 100% 66
2a0f:7840::/29 No ROA RIR databaseRIPE 326 51% 64

AS-SET

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

  • ROA: none7
ChangePrefix or setDetailFull-table peers
ROA: none193.28.14.0/24No ROA covers it. Add a ROA for AS6764, maxLength 24.673 of 673
ROA: none193.28.43.0/24No ROA covers it. Add a ROA for AS6764, maxLength 24.673 of 673
ROA: none193.28.51.0/24No ROA covers it. Add a ROA for AS6764, maxLength 24.673 of 673
ROA: none193.28.54.0/24No ROA covers it. Add a ROA for AS6764, maxLength 24.673 of 673
ROA: none195.246.0.0/19No ROA covers it. Add a ROA for AS6764, maxLength 19.673 of 673
ROA: none212.118.64.0/19No ROA covers it. Add a ROA for AS6764, maxLength 19.673 of 673
ROA: none2a0f:7840::/29No ROA covers it. Add a ROA for AS6764, maxLength 29.326 of 636

Route objects not announced

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