bgpreport

Network · data from 2026-11-12

AS274743 FASTWEB TELECOMUNICACOES

Registry name: AS274743 - FASTWEB TELECOMUNICACOES, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274743, 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.
186.251.212.0/23 No ROA None 672 100% 67
186.251.212.0/24 No ROA None 671 100% 67
186.251.213.0/24 No ROA None 669 99% 67
2804:92ec::/32 No ROA None 634 100% 67
2804:92ec::/33 No ROA None 634 100% 67
2804:92ec::/34 No ROA None 634 100% 67
2804:92ec:4000::/34 No ROA None 634 100% 67
2804:92ec:8000::/33 No ROA None 634 100% 67
2804:92ec:8000::/34 No ROA None 634 100% 67
2804:92ec:c000::/34 No ROA None 634 100% 67

AS-SET

AS274743'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 20 are in fix.csv.

  • ROA: none10
  • Route object: none10
ChangePrefix or setDetailFull-table peers
ROA: none186.251.212.0/23No ROA covers it. Add a ROA for AS274743, maxLength 23.672 of 673
Route object: none186.251.212.0/23No route object for it. Add a route object with origin AS274743 in the RIR database for the space.672 of 673
ROA: none186.251.212.0/24No ROA covers it. Add a ROA for AS274743, maxLength 24.671 of 673
Route object: none186.251.212.0/24No route object for it. Add a route object with origin AS274743 in the RIR database for the space.671 of 673
ROA: none186.251.213.0/24No ROA covers it. Add a ROA for AS274743, maxLength 24.669 of 673
Route object: none186.251.213.0/24No route object for it. Add a route object with origin AS274743 in the RIR database for the space.669 of 673
ROA: none2804:92ec::/32No ROA covers it. Add a ROA for AS274743, maxLength 32.634 of 636
Route object: none2804:92ec::/32No route object for it. Add a route object with origin AS274743 in the RIR database for the space.634 of 636
ROA: none2804:92ec::/33No ROA covers it. Add a ROA for AS274743, maxLength 33.634 of 636
Route object: none2804:92ec::/33No route object for it. Add a route object with origin AS274743 in the RIR database for the space.634 of 636
ROA: none2804:92ec::/34No ROA covers it. Add a ROA for AS274743, maxLength 34.634 of 636
Route object: none2804:92ec::/34No route object for it. Add a route object with origin AS274743 in the RIR database for the space.634 of 636
ROA: none2804:92ec:4000::/34No ROA covers it. Add a ROA for AS274743, maxLength 34.634 of 636
Route object: none2804:92ec:4000::/34No route object for it. Add a route object with origin AS274743 in the RIR database for the space.634 of 636
ROA: none2804:92ec:8000::/33No ROA covers it. Add a ROA for AS274743, maxLength 33.634 of 636
Route object: none2804:92ec:8000::/33No route object for it. Add a route object with origin AS274743 in the RIR database for the space.634 of 636
ROA: none2804:92ec:8000::/34No ROA covers it. Add a ROA for AS274743, maxLength 34.634 of 636
Route object: none2804:92ec:8000::/34No route object for it. Add a route object with origin AS274743 in the RIR database for the space.634 of 636
ROA: none2804:92ec:c000::/34No ROA covers it. Add a ROA for AS274743, maxLength 34.634 of 636
Route object: none2804:92ec:c000::/34No route object for it. Add a route object with origin AS274743 in the RIR database for the space.634 of 636

Route objects not announced

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