bgpreport

Network · data from 2026-11-12

AS200629 cloudio Advania Danmark A/S

Registry name: cloudio Advania Danmark A/S, DK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200629, 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.
2a0c:e040:126::/48 No ROA Nonecovered by 2a0c:e040::/29 634 100% 67
2a0c:e040:131::/48 No ROA Nonecovered by 2a0c:e040::/29 634 100% 67
2a0c:e040:1337::/48 No ROA Nonecovered by 2a0c:e040::/29 634 100% 67
193.228.76.0/22 No ROA RIR databaseRIPE 673 100% 66
193.228.76.0/24 No ROA RIR databaseRIPE 673 100% 66
193.228.79.0/24 No ROA RIR databaseRIPE 673 100% 66
2a0c:e040::/29 No ROA RIR databaseRIPE 634 100% 67

AS-SET

AS200629 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 12 are in fix.csv.

  • ROA: none7
  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a0c:e040:126::/48No ROA covers it. Add a ROA for AS200629, maxLength 48.634 of 636
Route object: none2a0c:e040:126::/48No route object for it. A route object for 2a0c:e040::/29 with origin AS200629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200629 in the RIR database for the space.634 of 636
ROA: none2a0c:e040:131::/48No ROA covers it. Add a ROA for AS200629, maxLength 48.634 of 636
Route object: none2a0c:e040:131::/48No route object for it. A route object for 2a0c:e040::/29 with origin AS200629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200629 in the RIR database for the space.634 of 636
ROA: none2a0c:e040:1337::/48No ROA covers it. Add a ROA for AS200629, maxLength 48.634 of 636
Route object: none2a0c:e040:1337::/48No route object for it. A route object for 2a0c:e040::/29 with origin AS200629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200629 in the RIR database for the space.634 of 636
ROA: none193.228.76.0/22No ROA covers it. Add a ROA for AS200629, maxLength 22.673 of 673
ROA: none193.228.76.0/24No ROA covers it. Add a ROA for AS200629, maxLength 24.673 of 673
ROA: none193.228.79.0/24No ROA covers it. Add a ROA for AS200629, maxLength 24.673 of 673
ROA: none2a0c:e040::/29No ROA covers it. Add a ROA for AS200629, maxLength 29.634 of 636

Route objects not announced

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

193.228.77.0/24RIPENo ROA
193.228.78.0/24RIPENo ROA

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.