bgpreport

Network · data from 2026-11-12

AS52978 RG3.Net Comercio e Servicos

Registry name: AS52978 - RG3.Net Comercio e Servicos Ltda., BR · PeeringDB

7IPv4 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
8No 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 AS52978, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS52978, 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.39.200.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
2804:46c::/32 No ROA Other IRR onlyRADB, TC 633 100% 67
177.39.200.0/24 No ROA Other IRR onlyRADB 207 31% 54
177.39.201.0/24 No ROA Other IRR onlyRADB 207 31% 54
177.39.202.0/24 No ROA Other IRR onlyRADB 207 31% 54
177.39.203.0/24 No ROA Other IRR onlyRADB 207 31% 54
177.39.200.0/23 No ROA Other IRR onlyRADB 206 31% 54
177.39.202.0/23 No ROA Other IRR onlyRADB 206 31% 54

AS-SET

AS52978'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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none177.39.200.0/22No ROA covers it. Add a ROA for AS52978, maxLength 22.672 of 673
Route object: RIR177.39.200.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:46c::/32No ROA covers it. Add a ROA for AS52978, maxLength 32.633 of 636
Route object: RIR2804:46c::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
ROA: none177.39.200.0/24No ROA covers it. Add a ROA for AS52978, maxLength 24.207 of 673
Route object: RIR177.39.200.0/24Route object only in RADB. Add it in the RIR database for the space.207 of 673
ROA: none177.39.201.0/24No ROA covers it. Add a ROA for AS52978, maxLength 24.207 of 673
Route object: RIR177.39.201.0/24Route object only in RADB. Add it in the RIR database for the space.207 of 673
ROA: none177.39.202.0/24No ROA covers it. Add a ROA for AS52978, maxLength 24.207 of 673
Route object: RIR177.39.202.0/24Route object only in RADB. Add it in the RIR database for the space.207 of 673
ROA: none177.39.203.0/24No ROA covers it. Add a ROA for AS52978, maxLength 24.207 of 673
Route object: RIR177.39.203.0/24Route object only in RADB. Add it in the RIR database for the space.207 of 673
ROA: none177.39.200.0/23No ROA covers it. Add a ROA for AS52978, maxLength 23.206 of 673
Route object: RIR177.39.200.0/23Route object only in RADB. Add it in the RIR database for the space.206 of 673
ROA: none177.39.202.0/23No ROA covers it. Add a ROA for AS52978, maxLength 23.206 of 673
Route object: RIR177.39.202.0/23Route object only in RADB. Add it in the RIR database for the space.206 of 673

Route objects not announced

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