bgpreport

Network · data from 2026-11-12

AS274669 AS274669 - CloudiNet Provedor de Internet

Registry name: AS274669 - CloudiNet Provedor de Internet, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274669, 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.
2804:91d8::/38 No ROA Other IRR onlyRADB 632 99% 67

AS-SET

AS274669 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: none1
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2804:91d8::/38No ROA covers it. Add a ROA for AS274669, maxLength 38.632 of 636
Route object: RIR2804:91d8::/38Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

2804:91d8::/32ALTDBNo ROA
2804:91d8:400::/38RADBNo ROA
2804:91d8:800::/38RADBNo 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.