bgpreport

Network · data from 2026-11-12

AS275723 Ademir Sulzenco & Cia

Registry name: AS275723 - Ademir Sulzenco & Cia LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS275723, 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.

151.247.175.0/24 Invalid: origin None 2 0%low visibility 2
2804:9894::/32 No ROA Other IRR onlyRADB 1 0%low visibility 1
177.201.211.0/24 Valid RIR databaseRADB, RIPE 671 100% 66

AS-SET

AS275723's PeeringDB record names no 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: origin1
  • ROA: none1
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin151.247.175.0/24ROAs covering it name AS834, not AS275723. If AS275723 should announce it, add a ROA for AS275723.2 of 673
Route object: none151.247.175.0/24No route object for it. Add a route object with origin AS275723 in the RIR database for the space.2 of 673
ROA: none2804:9894::/32No ROA covers it. Add a ROA for AS275723, maxLength 32.1 of 636
Route object: RIR2804:9894::/32Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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