Network · data from 2026-11-12

AS265174 AS265174 - MENTRIX TELECOM LTDA

Registry name: AS265174 - MENTRIX TELECOM LTDA, BR · not in PeeringDB

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

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

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

9Route objects not announced registered with origin AS265174, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265174, 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.204.0/22	Valid	Other IRR onlyRADB, TC	667 99%	67
2804:2bc4::/32	Valid	Other IRR onlyRADB, TC	635 100%	67
167.249.204.0/23	Valid	Other IRR onlyRADB, TC	34 5%low visibility	12
167.249.206.0/23	Valid	Other IRR onlyRADB, TC	31 5%low visibility	11
2804:2bc4:8000::/33	Valid	Other IRR onlyTC	28 4%low visibility	12

167.249.204.0/22

Valid

Other IRR onlyRADB, TC

667 99%

2804:2bc4::/32

Valid

Other IRR onlyRADB, TC

635 100%

167.249.204.0/23

Valid

Other IRR onlyRADB, TC

34 5%low visibility

167.249.206.0/23

Valid

Other IRR onlyRADB, TC

31 5%low visibility

2804:2bc4:8000::/33

Valid

Other IRR onlyTC

28 4%low visibility

AS-SET

AS265174 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: RIR5
Route object: not announced9

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	167.249.204.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	667 of 673
Route object: RIR	2804:2bc4::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	635 of 636
Route object: RIR	167.249.204.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	34 of 673
Route object: RIR	167.249.206.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	31 of 673
Route object: RIR	2804:2bc4:8000::/33	Route object only in TC. Add it in the RIR database for the space.	28 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

167.249.204.0/22

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

667 of 673

Route object: RIR

2804:2bc4::/32

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

635 of 636

Route object: RIR

167.249.204.0/23

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

34 of 673

Route object: RIR

167.249.206.0/23

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

31 of 673

Route object: RIR

2804:2bc4:8000::/33

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

28 of 636

Route objects not announced

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


167.249.204.0/24	RADB, TC	Valid
167.249.205.0/24	RADB, TC	Valid
167.249.206.0/24	RADB, TC	Valid
167.249.207.0/24	RADB, TC	Valid
2804:2bc4::/33	TC	Valid
2804:2bc4::/34	TC	Valid
2804:2bc4:4000::/34	TC	Valid
2804:2bc4:8000::/34	TC	Valid
2804:2bc4:c000::/34	TC	Valid

167.249.204.0/24

RADB, TC

Valid

167.249.205.0/24

RADB, TC

Valid

167.249.206.0/24

RADB, TC

Valid

167.249.207.0/24

RADB, TC

Valid

2804:2bc4::/33

Valid

2804:2bc4::/34

Valid

2804:2bc4:4000::/34

Valid

2804:2bc4:8000::/34

Valid

2804:2bc4:c000::/34

Valid

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.