bgpreport

Network · data from 2026-11-12

AS52647 AS52647 - Melp Comercio & Representacoes Ltda ME

Registry name: AS52647 - Melp Comercio & Representacoes Ltda ME, BR · not in PeeringDB

4IPv4 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
5No 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 AS52647, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS52647, 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.
177.125.197.0/24 No ROA Other IRR onlyRADB 672 100% 67
177.125.198.0/24 No ROA Other IRR onlyRADB 672 100% 67
177.125.196.0/24 No ROA Other IRR onlyRADB 670 100% 67
177.125.199.0/24 No ROA Other IRR onlyRADB 670 100% 67
2804:d9c::/32 No ROA Other IRR onlyBBOI, NTTCOM, RADB 635 100% 69

AS-SET

AS52647 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 13 are in fix.csv.

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none177.125.197.0/24No ROA covers it. Add a ROA for AS52647, maxLength 24.672 of 673
Route object: RIR177.125.197.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.125.198.0/24No ROA covers it. Add a ROA for AS52647, maxLength 24.672 of 673
Route object: RIR177.125.198.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.125.196.0/24No ROA covers it. Add a ROA for AS52647, maxLength 24.670 of 673
Route object: RIR177.125.196.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.125.199.0/24No ROA covers it. Add a ROA for AS52647, maxLength 24.670 of 673
Route object: RIR177.125.199.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:d9c::/32No ROA covers it. Add a ROA for AS52647, maxLength 32.635 of 636
Route object: RIR2804:d9c::/32Route object only in BBOI, NTTCOM, RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

177.125.196.0/22BBOI, NTTCOM, RADBNo ROA
177.125.196.0/23RADBNo ROA
177.125.198.0/23RADBNo 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.