Network · data from 2026-11-12

AS267787 AS267787 - MENDOZA MENDOZA CARLOS ALFREDO(TECGLO TECNOLOGIA GLOBAL)

Registry name: AS267787 - MENDOZA MENDOZA CARLOS ALFREDO(TECGLO TECNOLOGIA GLOBAL), EC · not in PeeringDB

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

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

4Route objects not announced registered with origin AS267787, seen from no peer

Announced routes

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


45.171.160.0/24	Valid	Other IRR onlyRADB	667 99%	67
45.171.161.0/24	Valid	Other IRR onlyRADB	667 99%	67
45.171.162.0/24	Valid	Other IRR onlyRADB	667 99%	67
45.171.163.0/24	Valid	Other IRR onlyRADB	663 99%	67
45.171.160.0/22	Valid	RIR databaseLACNIC, RADB	663 99%	67
2803:4fa0:2::/48	Valid	RIR databaseLACNIC	634 100%	67
2803:4fa0:3::/48	Valid	RIR databaseLACNIC	634 100%	67
2803:4fa0:4::/48	Valid	RIR databaseLACNIC	634 100%	67
2803:4fa0:7::/48	Valid	RIR databaseLACNIC	634 100%	67
2803:4fa0:8::/48	Valid	RIR databaseLACNIC	634 100%	67
2803:4fa0:12::/48	Valid	RIR databaseLACNIC	634 100%	67
2803:4fa0:9::/48	Valid	RIR databaseLACNIC	633 100%	67
2803:4fa0:13::/48	Valid	RIR databaseLACNIC	633 100%	67

AS-SET

AS267787 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: RIR4
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.171.160.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	45.171.161.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	45.171.162.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	45.171.163.0/24	Route object only in RADB. Add it in the RIR database for the space.	663 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.171.160.0/24

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

667 of 673

Route object: RIR

45.171.161.0/24

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

667 of 673

Route object: RIR

45.171.162.0/24

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

667 of 673

Route object: RIR

45.171.163.0/24

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

663 of 673

Route objects not announced

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


2803:4fa0::/32	LACNIC	Valid
2803:4fa0:1::/48	LACNIC	Valid
2803:4fa0:5::/48	LACNIC	Valid
2803:4fa0:6::/48	LACNIC	Valid

2803:4fa0::/32

LACNIC

Valid

2803:4fa0:1::/48

LACNIC

Valid

2803:4fa0:5::/48

LACNIC

Valid

2803:4fa0:6::/48

LACNIC

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.