bgpreport

Network · data from 2026-11-12

AS264391 Newnet Telecom Ltda

Registry name: AS264391 - Newnet Telecom Ltda, BR · PeeringDB

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

Announced routes

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

131.161.180.0/23 No ROA Nonecovered by 131.161.180.0/22 667 99% 67
2804:1dc0::/33 No ROA Nonecovered by 2804:1dc0::/32 633 100% 67
131.161.182.0/23 No ROA Nonecovered by 131.161.180.0/22 2 0%low visibility 2
2804:1dc0:8000::/33 No ROA Nonecovered by 2804:1dc0::/32 1 0%low visibility 1
131.161.180.0/24 No ROA Other IRR onlyRADB 667 99% 67
131.161.181.0/24 No ROA Other IRR onlyRADB 667 99% 67
131.161.182.0/24 No ROA Other IRR onlyRADB 667 99% 67
131.161.183.0/24 No ROA Other IRR onlyRADB 667 99% 67

AS-SET

AS264391'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 18 are in fix.csv.

  • ROA: none8
  • Route object: none4
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none131.161.180.0/23No ROA covers it. Add a ROA for AS264391, maxLength 23.667 of 673
Route object: none131.161.180.0/23No route object for it. A route object for 131.161.180.0/22 with origin AS264391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264391 in the RIR database for the space.667 of 673
ROA: none2804:1dc0::/33No ROA covers it. Add a ROA for AS264391, maxLength 33.633 of 636
Route object: none2804:1dc0::/33No route object for it. A route object for 2804:1dc0::/32 with origin AS264391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264391 in the RIR database for the space.633 of 636
ROA: none131.161.182.0/23No ROA covers it. Add a ROA for AS264391, maxLength 23.2 of 673
Route object: none131.161.182.0/23No route object for it. A route object for 131.161.180.0/22 with origin AS264391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264391 in the RIR database for the space.2 of 673
ROA: none2804:1dc0:8000::/33No ROA covers it. Add a ROA for AS264391, maxLength 33.1 of 636
Route object: none2804:1dc0:8000::/33No route object for it. A route object for 2804:1dc0::/32 with origin AS264391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264391 in the RIR database for the space.1 of 636
ROA: none131.161.180.0/24No ROA covers it. Add a ROA for AS264391, maxLength 24.667 of 673
Route object: RIR131.161.180.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none131.161.181.0/24No ROA covers it. Add a ROA for AS264391, maxLength 24.667 of 673
Route object: RIR131.161.181.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none131.161.182.0/24No ROA covers it. Add a ROA for AS264391, maxLength 24.667 of 673
Route object: RIR131.161.182.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none131.161.183.0/24No ROA covers it. Add a ROA for AS264391, maxLength 24.667 of 673
Route object: RIR131.161.183.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

131.161.180.0/22RADBNo ROA
2804:1dc0::/32RADBNo 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.