bgpreport

Network · data from 2026-11-12

AS39913 cloud4you Manuel Wannemacher

Registry name: cloud4you Manuel Wannemacher, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39913, 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.
83.242.32.0/22 No ROA RIR databaseRIPE 673 100% 66
91.132.152.0/22 No ROA RIR databaseRIPE 673 100% 66
193.93.240.0/22 No ROA RIR databaseRIPE 673 100% 66
2001:67c:207c::/48 No ROA RIR databaseRIPE 635 100% 67
2a09:c880::/29 No ROA RIR databaseRIPE 634 100% 67

AS-SET

AS39913 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 5 are in fix.csv.

  • ROA: none5
ChangePrefix or setDetailFull-table peers
ROA: none83.242.32.0/22No ROA covers it. Add a ROA for AS39913, maxLength 22.673 of 673
ROA: none91.132.152.0/22No ROA covers it. Add a ROA for AS39913, maxLength 22.673 of 673
ROA: none193.93.240.0/22No ROA covers it. Add a ROA for AS39913, maxLength 22.673 of 673
ROA: none2001:67c:207c::/48No ROA covers it. Add a ROA for AS39913, maxLength 48.635 of 636
ROA: none2a09:c880::/29No ROA covers it. Add a ROA for AS39913, maxLength 29.634 of 636

Route objects not announced

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