bgpreport

Network · data from 2026-11-12

AS271071 AS271071 - NAVEGAI SERVICOS DE TELECOMUNICACOES E INFORMATICA

Registry name: AS271071 - NAVEGAI SERVICOS DE TELECOMUNICACOES E INFORMATICA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271071, 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.48.92.0/23 Invalid: maxLength Nonecovered by 179.48.92.0/22 2 0%low visibility 2
179.48.94.0/23 Invalid: maxLength Nonecovered by 179.48.92.0/22 2 0%low visibility 2
179.48.92.0/22 Valid Other IRR onlyALTDB, TC 669 99% 67

AS-SET

AS271071 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 10 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength179.48.92.0/23ROA 179.48.92.0/22 AS271071 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 179.48.92.0/23.2 of 673
Route object: none179.48.92.0/23No route object for it. A route object for 179.48.92.0/22 with origin AS271071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271071 in the RIR database for the space.2 of 673
ROA: maxLength179.48.94.0/23ROA 179.48.92.0/22 AS271071 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 179.48.94.0/23.2 of 673
Route object: none179.48.94.0/23No route object for it. A route object for 179.48.92.0/22 with origin AS271071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271071 in the RIR database for the space.2 of 673
Route object: RIR179.48.92.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

179.48.92.0/24ALTDBValid
179.48.93.0/24ALTDBValid
179.48.94.0/24ALTDBValid
179.48.95.0/24ALTDBValid
2804:75d0::/32TCNo 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.