bgpreport

Network · data from 2026-11-12

AS57063 PUZL-AS GPU Computing OU

Registry name: PUZL-AS GPU Computing OU, EE · not in PeeringDB

1IPv4 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
1Route objects not announced registered with origin AS57063, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS57063, 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.
2001:67c:f74::/48 No ROA RIR databaseRIPE 636 100% 67
213.5.72.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS57063 isn't in PeeringDB, where networks name their 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: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:f74::/48No ROA covers it. Add a ROA for AS57063, maxLength 48.636 of 636

Route objects not announced

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

91.236.201.0/24RIPEValid

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.