Network · data from 2026-11-12

AS265192 MNET LTDA

Registry name: AS265192 - Mnet LTDA, BR · PeeringDB

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

6IPv6 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

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

3Route objects not announced registered with origin AS265192, seen from no peer

Announced routes

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


167.249.144.0/22	Valid	Other IRR onlyRADB, TC	671 100%	66
2804:2c10::/32	Valid	Other IRR onlyRADB, TC	632 99%	67
2804:2c10::/33	Valid	Other IRR onlyRADB	632 99%	67
2804:2c10::/34	Valid	Other IRR onlyRADB	632 99%	67
2804:2c10:4000::/34	Valid	Other IRR onlyRADB	632 99%	67
2804:2c10:8000::/33	Valid	Other IRR onlyRADB	632 99%	67
2804:2c10:8000::/34	Valid	Other IRR onlyRADB	632 99%	67
167.249.145.0/24	Valid	Other IRR onlyRADB	122 18%	43
167.249.147.0/24	Valid	Other IRR onlyRADB	122 18%	43
167.249.144.0/24	Valid	Other IRR onlyRADB	120 18%	42
167.249.146.0/24	Valid	Other IRR onlyRADB	120 18%	42

AS-SET

PeeringDB's irr_as_set for AS265192: AS265192:AS-MNET-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS265192 isn't in the set, or no route object for AS265192 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS265192 in it	Not covered
AS265192:AS-MNET-ALL	TC	11	2	137	Yes	0

Name

Database

ASNs

Sets

Route objects

AS265192 in it

Not covered

AS265192:AS-MNET-ALL

137

Yes

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: RIR11
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	167.249.144.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:2c10::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	632 of 636
Route object: RIR	2804:2c10::/33	Route object only in RADB. Add it in the RIR database for the space.	632 of 636
Route object: RIR	2804:2c10::/34	Route object only in RADB. Add it in the RIR database for the space.	632 of 636
Route object: RIR	2804:2c10:4000::/34	Route object only in RADB. Add it in the RIR database for the space.	632 of 636
Route object: RIR	2804:2c10:8000::/33	Route object only in RADB. Add it in the RIR database for the space.	632 of 636
Route object: RIR	2804:2c10:8000::/34	Route object only in RADB. Add it in the RIR database for the space.	632 of 636
Route object: RIR	167.249.145.0/24	Route object only in RADB. Add it in the RIR database for the space.	122 of 673
Route object: RIR	167.249.147.0/24	Route object only in RADB. Add it in the RIR database for the space.	122 of 673
Route object: RIR	167.249.144.0/24	Route object only in RADB. Add it in the RIR database for the space.	120 of 673
Route object: RIR	167.249.146.0/24	Route object only in RADB. Add it in the RIR database for the space.	120 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

167.249.144.0/22

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

671 of 673

Route object: RIR

2804:2c10::/32

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

632 of 636

Route object: RIR

2804:2c10::/33