bgpreport

Network · data from 2026-11-12

AS61908 AS61908 - Nova Net Telecomunicacoes Ltda

Registry name: AS61908 - Nova Net Telecomunicacoes Ltda, BR · not in PeeringDB

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

Announced routes

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

138.121.204.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
168.197.244.0/22 Valid Other IRR onlyRADB 671 100% 67
132.255.40.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
179.124.184.0/21 Valid Other IRR onlyRADB, TC 670 100% 67
2804:16a0::/32 Valid Other IRR onlyRADB, TC 635 100% 67
132.255.40.0/23 Valid Other IRR onlyRADB 1 0%low visibility 1
132.255.42.0/23 Valid Other IRR onlyRADB 1 0%low visibility 1
138.121.204.0/23 Valid Other IRR onlyRADB 1 0%low visibility 1
138.121.206.0/23 Valid Other IRR onlyRADB 1 0%low visibility 1
168.197.244.0/23 Valid Other IRR onlyRADB 1 0%low visibility 1
168.197.246.0/23 Valid Other IRR onlyRADB 1 0%low visibility 1
179.124.184.0/22 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
179.124.188.0/22 Valid Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

AS61908 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 14 are in fix.csv.

  • Route object: RIR13
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR138.121.204.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.197.244.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR132.255.40.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR179.124.184.0/21Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:16a0::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR132.255.40.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR132.255.42.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR138.121.204.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR138.121.206.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR168.197.244.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR168.197.246.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR179.124.184.0/22Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673
Route object: RIR179.124.188.0/22Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

132.255.40.0/24TCValid

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.