bgpreport

Network · data from 2026-11-12

AS275765 AS275765 - SERRA CLOUD LTDA

Registry name: AS275765 - SERRA CLOUD LTDA, 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
2Route objects not announced registered with origin AS275765, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS275765, 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:993c::/32 No ROA Other IRR onlyTC 635 100% 68

AS-SET

AS275765 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 4 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:993c::/32No ROA covers it. Add a ROA for AS275765, maxLength 32.635 of 636
Route object: RIR2804:993c::/32Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

131.255.160.0/24TCNo ROA
131.255.161.0/24TCNo 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.