bgpreport

Network · data from 2026-11-12

AS271945 AZTECA TELECOM

Registry name: AS271945 - AZTECA TELECOM S.R.L., DO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271945, 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.
2803:e610:8200::/40 Valid Nonecovered by 2803:e610::/32 632 99% 67
2803:e610:8300::/40 Valid Nonecovered by 2803:e610::/32 632 99% 67
2803:e610:8000::/40 Valid Other IRR onlyRADB 633 100% 69
2803:e610:8100::/40 Valid Other IRR onlyRADB 633 100% 69
2803:e610:f000::/36 Valid Other IRR onlyRADB 633 100% 69
190.110.32.0/24 Valid RIR databaseLACNIC 668 99% 67
190.110.33.0/24 Valid RIR databaseLACNIC 667 99% 67
2803:e610::/32 Valid RIR databaseLACNIC, RADB 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS271945: AS271945:AS-CLIENTES. 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 (AS271945 isn't in the set, or no route object for AS271945 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.

NameDatabaseASNsSets Route objectsAS271945 in itNot covered
AS271945:AS-CLIENTES LACNIC 461388 No 8

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

  • Route object: none2
  • Route object: RIR3
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: none2803:e610:8200::/40No route object for it. A route object for 2803:e610::/32 with origin AS271945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271945 in the RIR database for the space.632 of 636
Route object: none2803:e610:8300::/40No route object for it. A route object for 2803:e610::/32 with origin AS271945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271945 in the RIR database for the space.632 of 636
Route object: RIR2803:e610:8000::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2803:e610:8100::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2803:e610:f000::/36Route object only in RADB. Add it in the RIR database for the space.633 of 636
AS-SET: own ASNAS271945:AS-CLIENTESAS271945 isn't in AS271945:AS-CLIENTES (LACNIC) once expanded. Add AS271945 to it.

Route objects not announced

Every route object with origin AS271945 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.