bgpreport

Network · data from 2026-11-12

AS61765 Forza Telecom

Registry name: AS61765 - Forza Telecomunicacoes LTDA, BR · PeeringDB

8IPv4 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
9No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
15Route objects not announced registered with origin AS61765, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61765, 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.
38.56.196.0/24 No ROA Other IRR onlyRADB 672 100% 66
38.56.197.0/24 No ROA Other IRR onlyRADB 672 100% 66
181.189.110.0/24 No ROA Other IRR onlyRADB 672 100% 66
200.71.120.0/22 No ROA Other IRR onlyRADB 672 100% 66
200.71.120.0/24 No ROA Other IRR onlyRADB 672 100% 66
200.71.121.0/24 No ROA Other IRR onlyRADB 672 100% 66
200.71.122.0/24 No ROA Other IRR onlyRADB 671 100% 66
200.71.123.0/24 No ROA Other IRR onlyRADB 671 100% 66
2804:18f4::/32 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

AS61765'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 33 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none38.56.196.0/24No ROA covers it. Add a ROA for AS61765, maxLength 24.672 of 673
Route object: RIR38.56.196.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.56.197.0/24No ROA covers it. Add a ROA for AS61765, maxLength 24.672 of 673
Route object: RIR38.56.197.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.189.110.0/24No ROA covers it. Add a ROA for AS61765, maxLength 24.672 of 673
Route object: RIR181.189.110.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.71.120.0/22No ROA covers it. Add a ROA for AS61765, maxLength 22.672 of 673
Route object: RIR200.71.120.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.71.120.0/24No ROA covers it. Add a ROA for AS61765, maxLength 24.672 of 673
Route object: RIR200.71.120.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.71.121.0/24No ROA covers it. Add a ROA for AS61765, maxLength 24.672 of 673
Route object: RIR200.71.121.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.71.122.0/24No ROA covers it. Add a ROA for AS61765, maxLength 24.671 of 673
Route object: RIR200.71.122.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.71.123.0/24No ROA covers it. Add a ROA for AS61765, maxLength 24.671 of 673
Route object: RIR200.71.123.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:18f4::/32No ROA covers it. Add a ROA for AS61765, maxLength 32.635 of 636
Route object: RIR2804:18f4::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

38.56.196.0/23RADBNo ROA
200.71.120.0/23RADBNo ROA
200.71.122.0/23RADBNo ROA
2804:18f4::/33RADBNo ROA
2804:18f4:2000::/48RADBNo ROA
2804:18f4:3000::/48RADBNo ROA
2804:18f4:3100::/48RADBNo ROA
2804:18f4:3400::/48RADBNo ROA
2804:18f4:3600::/39RADBNo ROA
2804:18f4:3800::/39RADBNo ROA
2804:18f4:4000::/42RADBNo ROA
2804:18f4:4000::/45RADBNo ROA
2804:18f4:4100::/45RADBNo ROA
2804:18f4:4102::/48RADBNo ROA
2804:18f4:8000::/33RADBNo 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.