bgpreport

Network · data from 2026-11-12

AS270657 AS270657 - FNET TELECOM

Registry name: AS270657 - FNET TELECOM, BR · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 100.0% with a route object
4IPv6 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
7Route objects not announced registered with origin AS270657, seen from no peer

Announced routes

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

179.191.42.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
179.191.43.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
179.191.41.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
179.191.40.0/24 No ROA Other IRR onlyRADB, TC 667 99% 67
2804:6f64::/34 No ROA Other IRR onlyTC 631 99% 67
2804:6f64:8000::/34 No ROA Other IRR onlyTC 630 99% 67
2804:6f64:8020::/44 No ROA Other IRR onlyRADB 630 99% 67
2804:6f64:8030::/44 No ROA Other IRR onlyRADB 630 99% 67

AS-SET

AS270657 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 23 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none179.191.42.0/24No ROA covers it. Add a ROA for AS270657, maxLength 24.672 of 673
Route object: RIR179.191.42.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none179.191.43.0/24No ROA covers it. Add a ROA for AS270657, maxLength 24.672 of 673
Route object: RIR179.191.43.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none179.191.41.0/24No ROA covers it. Add a ROA for AS270657, maxLength 24.668 of 673
Route object: RIR179.191.41.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none179.191.40.0/24No ROA covers it. Add a ROA for AS270657, maxLength 24.667 of 673
Route object: RIR179.191.40.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none2804:6f64::/34No ROA covers it. Add a ROA for AS270657, maxLength 34.631 of 636
Route object: RIR2804:6f64::/34Route object only in TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:6f64:8000::/34No ROA covers it. Add a ROA for AS270657, maxLength 34.630 of 636
Route object: RIR2804:6f64:8000::/34Route object only in TC. Add it in the RIR database for the space.630 of 636
ROA: none2804:6f64:8020::/44No ROA covers it. Add a ROA for AS270657, maxLength 44.630 of 636
Route object: RIR2804:6f64:8020::/44Route object only in RADB. Add it in the RIR database for the space.630 of 636
ROA: none2804:6f64:8030::/44No ROA covers it. Add a ROA for AS270657, maxLength 44.630 of 636
Route object: RIR2804:6f64:8030::/44Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

179.191.40.0/22RADB, TCNo ROA
179.191.40.0/23RADBNo ROA
179.191.42.0/23RADB, TCNo ROA
2804:6f64::/32RADB, TCNo ROA
2804:6f64:4000::/34TCNo ROA
2804:6f64:c000::/34TCNo ROA
2804:6f64:ff80::/41RADBNo 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.