bgpreport

Network · data from 2026-11-12

AS271473 AS271473 - NewFibra Telecomunicacoes - ME

Registry name: AS271473 - NewFibra Telecomunicacoes - ME, BR · not in PeeringDB

6IPv4 routes 0.0% RPKI valid · 100.0% with a route object
3IPv6 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
2Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS271473, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271473, 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.
181.174.208.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
181.174.208.0/24 No ROA Other IRR onlyTC 671 100% 66
181.174.209.0/24 No ROA Other IRR onlyTC 671 100% 66
181.174.211.0/24 No ROA Other IRR onlyTC 671 100% 67
2804:7c10::/32 No ROA Other IRR onlyRADB, TC 634 100% 67
2804:7c10::/33 No ROA Other IRR onlyRADB 633 100% 67
2804:7c10:8000::/33 No ROA Other IRR onlyRADB 633 100% 67
181.174.210.0/23 No ROA Other IRR onlyTC 12 2%low visibility 9
181.174.210.0/24 No ROA Other IRR onlyTC 7 1%low visibility 5

AS-SET

AS271473 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 19 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none181.174.208.0/22No ROA covers it. Add a ROA for AS271473, maxLength 22.671 of 673
Route object: RIR181.174.208.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none181.174.208.0/24No ROA covers it. Add a ROA for AS271473, maxLength 24.671 of 673
Route object: RIR181.174.208.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none181.174.209.0/24No ROA covers it. Add a ROA for AS271473, maxLength 24.671 of 673
Route object: RIR181.174.209.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none181.174.211.0/24No ROA covers it. Add a ROA for AS271473, maxLength 24.671 of 673
Route object: RIR181.174.211.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:7c10::/32No ROA covers it. Add a ROA for AS271473, maxLength 32.634 of 636
Route object: RIR2804:7c10::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:7c10::/33No ROA covers it. Add a ROA for AS271473, maxLength 33.633 of 636
Route object: RIR2804:7c10::/33Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2804:7c10:8000::/33No ROA covers it. Add a ROA for AS271473, maxLength 33.633 of 636
Route object: RIR2804:7c10:8000::/33Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none181.174.210.0/23No ROA covers it. Add a ROA for AS271473, maxLength 23.12 of 673
Route object: RIR181.174.210.0/23Route object only in TC. Add it in the RIR database for the space.12 of 673
ROA: none181.174.210.0/24No ROA covers it. Add a ROA for AS271473, maxLength 24.7 of 673
Route object: RIR181.174.210.0/24Route object only in TC. Add it in the RIR database for the space.7 of 673

Route objects not announced

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

181.174.208.0/23TCNo 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.