Network · data from 2026-11-12

AS61731 AS61731 - Work 349 Internet Provedores ltda - ME

Registry name: AS61731 - Work 349 Internet Provedores ltda - ME, BR · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 20.0% with a route object

3IPv6 routes 100.0% RPKI valid · 33.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 6 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS61731, seen from no peer

Announced routes

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


2804:1b7c::/33	Valid	Nonecovered by 2804:1b7c::/32	338 53%	65
2804:1b7c:8000::/33	Valid	Nonecovered by 2804:1b7c::/32	338 53%	65
131.72.160.0/24	Valid	Nonecovered by 131.72.160.0/22	152 23%	51
131.72.161.0/24	Valid	Nonecovered by 131.72.160.0/22	152 23%	51
131.72.162.0/24	Valid	Nonecovered by 131.72.160.0/22	152 23%	51
131.72.163.0/24	Valid	Nonecovered by 131.72.160.0/22	152 23%	51
131.72.160.0/22	Valid	Other IRR onlyALTDB, NTTCOM, RADB, TC	669 99%	67
2804:1b7c::/32	Valid	Other IRR onlyNTTCOM, TC	635 100%	67

AS-SET

AS61731 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 8 are in fix.csv.

Route object: none6
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:1b7c::/33	No route object for it. A route object for 2804:1b7c::/32 with origin AS61731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61731 in the RIR database for the space.	338 of 636
Route object: none	2804:1b7c:8000::/33	No route object for it. A route object for 2804:1b7c::/32 with origin AS61731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61731 in the RIR database for the space.	338 of 636
Route object: none	131.72.160.0/24	No route object for it. A route object for 131.72.160.0/22 with origin AS61731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61731 in the RIR database for the space.	152 of 673
Route object: none	131.72.161.0/24	No route object for it. A route object for 131.72.160.0/22 with origin AS61731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61731 in the RIR database for the space.	152 of 673
Route object: none	131.72.162.0/24	No route object for it. A route object for 131.72.160.0/22 with origin AS61731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61731 in the RIR database for the space.	152 of 673
Route object: none	131.72.163.0/24	No route object for it. A route object for 131.72.160.0/22 with origin AS61731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61731 in the RIR database for the space.	152 of 673
Route object: RIR	131.72.160.0/22	Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2804:1b7c::/32	Route object only in NTTCOM, TC. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:1b7c::/33

No route object for it. A route object for 2804:1b7c::/32 with origin AS61731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61731 in the RIR database for the space.

338 of 636

Route object: none

2804:1b7c:8000::/33

338 of 636

Route object: none

131.72.160.0/24

No route object for it. A route object for 131.72.160.0/22 with origin AS61731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61731 in the RIR database for the space.

152 of 673

Route object: none

131.72.161.0/24

152 of 673

Route object: none

131.72.162.0/24

152 of 673

Route object: none

131.72.163.0/24

152 of 673

Route object: RIR

131.72.160.0/22

Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.

669 of 673

Route object: RIR

2804:1b7c::/32

Route object only in NTTCOM, TC. Add it in the RIR database for the space.

635 of 636

Route objects not announced

Every route object with origin AS61731 is announced.

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.