bgpreport

Network · data from 2026-11-12

AS205243 CLOUDNOW-AS CloudNow GmbH

Registry name: CLOUDNOW-AS CloudNow GmbH, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205243, 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.
45.144.200.0/22 No ROA RIR databaseRIPE 673 100% 66
2a0e:f2c0::/29 No ROA RIR databaseRIPE 635 100% 69
185.215.200.0/22 Valid RIR databaseRIPE 673 100% 66
185.224.200.0/22 Valid RIR databaseRIPE 673 100% 66
2a0b:adc0::/29 Valid RIR databaseRIPE 635 100% 69
2a0d:3c00::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS205243 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: none2
ChangePrefix or setDetailFull-table peers
ROA: none45.144.200.0/22No ROA covers it. Add a ROA for AS205243, maxLength 22.673 of 673
ROA: none2a0e:f2c0::/29No ROA covers it. Add a ROA for AS205243, maxLength 29.635 of 636

Route objects not announced

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