bgpreport

Network · data from 2026-11-12

AS52692 AGNET BANDA LARGA

Registry name: AS52692 - CARVALHO E SILVA LTDA, BR · PeeringDB

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

Announced routes

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

170.246.136.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
177.72.220.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
170.246.136.0/23 Valid Other IRR onlyTC 671 100% 67
170.246.138.0/23 Valid Other IRR onlyTC 671 100% 67
177.72.220.0/23 Valid Other IRR onlyTC 669 99% 67
177.72.222.0/23 Valid Other IRR onlyTC 669 99% 67
2804:2ef8::/32 Valid Other IRR onlyRADB, TC 633 100% 67
2804:2ef8::/33 Valid Other IRR onlyTC 632 99% 67
2804:2ef8:8000::/33 Valid Other IRR onlyTC 630 99% 67

AS-SET

AS52692'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 21 are in fix.csv.

  • Route object: RIR9
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: RIR170.246.136.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.72.220.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.246.136.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.246.138.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.72.220.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.72.222.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:2ef8::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:2ef8::/33Route object only in TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:2ef8:8000::/33Route object only in TC. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

170.246.136.0/24TCValid
170.246.137.0/24TCValid
170.246.138.0/24TCValid
170.246.139.0/24TCValid
177.72.220.0/24TCValid
177.72.221.0/24TCValid
177.72.222.0/24TCValid
177.72.223.0/24TCValid
2804:2ef8::/34TCValid
2804:2ef8:4000::/34TCValid
2804:2ef8:8000::/34TCValid
2804:2ef8:c000::/34TCValid

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.