bgpreport

Network · data from 2026-11-12

AS52616 AS52616 - SUDONET Solucoes em Telecomunicacoes Ltda

Registry name: AS52616 - SUDONET Solucoes em Telecomunicacoes Ltda, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52616, 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.
181.233.148.0/22 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
177.124.52.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 66
2804:17a0::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS52616 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 6 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none181.233.148.0/22No ROA covers it. Add a ROA for AS52616, maxLength 22.672 of 673
Route object: RIR181.233.148.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.124.52.0/22No ROA covers it. Add a ROA for AS52616, maxLength 22.671 of 673
Route object: RIR177.124.52.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:17a0::/32No ROA covers it. Add a ROA for AS52616, maxLength 32.636 of 636
Route object: RIR2804:17a0::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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