bgpreport

Network · data from 2026-11-12

AS35360 GarguNet

Registry name: GARGUNET Frederic Gargula, CH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35360, 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.
0.0.0.0/0 bogon No ROA None 0 0%low visibility 1
45.66.4.0/22 Valid RIR databaseRIPE 673 100% 66
45.66.5.0/24 Valid RIR databaseRIPE 670 100% 66
45.66.6.0/24 Valid RIR databaseRIPE 670 100% 66
2a09:5fc0::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

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

  • Bogon prefix1
ChangePrefix or setDetailFull-table peers
Bogon prefix0.0.0.0/0In IANA's special-purpose registry: default route.0 of 673

Route objects not announced

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