bgpreport

Network · data from 2026-11-12

AS208948 RECYCLED-CLOUD-AS e-Durable SA

Registry name: RECYCLED-CLOUD-AS e-Durable SA, CH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208948, 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.
2a0d:d9c5::/32 Valid Nonecovered by 2a0d:d9c0::/29 634 100% 67
45.134.133.0/24 Valid RIR databaseRIPE 671 100% 66
45.134.135.0/24 Valid RIR databaseRIPE 671 100% 66
45.134.134.0/24 Valid RIR databaseRIPE 669 99% 67
2a0d:d9c3::/32 Valid RIR databaseRIPE 636 100% 69
2a0d:d9c4::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS208948 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 9 are in fix.csv.

  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none2a0d:d9c5::/32No route object for it. A route object for 2a0d:d9c0::/29 with origin AS208948 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208948 in the RIR database for the space.634 of 636

Route objects not announced

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

45.134.132.0/24RIPEValid
154.16.23.0/24AFRINICInvalid: origin
2a0d:d9c0::/29RIPENo ROA
2a0d:d9c0::/32RIPEValid
2a0d:d9c1::/32RIPENo ROA
2a0d:d9c2::/32RIPENo ROA
2a0d:d9c2:40::/48RIPENo ROA
2a0d:d9c3::/48RIPEValid

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.