bgpreport

Network · data from 2026-11-12

AS265620 UFINET MEXICO

Registry name: AS265620 - UFINET MEXICO S. DE R.L. DE C.V., MX · PeeringDB

12IPv4 routes 91.7% RPKI valid · 75.0% with a route object
4IPv6 routes 75.0% RPKI valid · 25.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 6 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS265620, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265620, 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:e880:8100::/48 Invalid: origin Other origin only 24 4%low visibility 14
38.226.201.0/24 No ROA None 90 13% 42
181.78.223.0/24 Valid None 672 100% 67
186.33.62.0/24 Valid None 672 100% 67
2806:3a0:1002::/48 Valid Nonecovered by 2806:3a0::/32 636 100% 67
2806:3a0:100e::/48 Valid Nonecovered by 2806:3a0::/32 636 100% 67
45.189.61.0/24 Valid Other IRR onlyRADB 673 100% 67
45.189.63.0/24 Valid Other IRR onlyRADB 673 100% 67
181.78.220.0/24 Valid Other IRR onlyRADB 673 100% 67
181.78.221.0/24 Valid Other IRR onlyRADB 673 100% 67
45.189.62.0/24 Valid Other IRR onlyRADB 672 100% 67
181.78.222.0/24 Valid Other IRR onlyRADB 672 100% 67
190.61.32.0/24 Valid Other IRR onlyRADB 672 100% 67
45.189.60.0/24 Valid Other IRR onlyRADB 659 98% 67
38.19.253.0/24 Valid RIR databaseARIN 671 100% 67
2806:3a0::/32 Valid RIR databaseLACNIC, RADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS265620: AS265620:AS-UFMX. 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 (AS265620 isn't in the set, or no route object for AS265620 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 objectsAS265620 in itNot covered
AS265620:AS-UFMX LACNIC 121996 No 16

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

  • ROA: origin1
  • ROA: none1
  • Route object: none6
  • Route object: RIR8
  • AS-SET: own ASN1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin2803:e880:8100::/48ROAs covering it name AS52468, not AS265620. If AS265620 should announce it, add a ROA for AS265620.24 of 636
Route object: none2803:e880:8100::/48Route objects for it name AS52468. Add a route object with origin AS265620 in the RIR database for the space.24 of 636
ROA: none38.226.201.0/24No ROA covers it. Add a ROA for AS265620, maxLength 24.90 of 673
Route object: none38.226.201.0/24No route object for it. Add a route object with origin AS265620 in the RIR database for the space.90 of 673
Route object: none181.78.223.0/24No route object for it. Add a route object with origin AS265620 in the RIR database for the space.672 of 673
Route object: none186.33.62.0/24No route object for it. Add a route object with origin AS265620 in the RIR database for the space.672 of 673
Route object: none2806:3a0:1002::/48No route object for it. A route object for 2806:3a0::/32 with origin AS265620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265620 in the RIR database for the space.636 of 636
Route object: none2806:3a0:100e::/48No route object for it. A route object for 2806:3a0::/32 with origin AS265620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265620 in the RIR database for the space.636 of 636
Route object: RIR45.189.61.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR45.189.63.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR181.78.220.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR181.78.221.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR45.189.62.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR181.78.222.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.61.32.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.189.60.0/24Route object only in RADB. Add it in the RIR database for the space.659 of 673
AS-SET: own ASNAS265620:AS-UFMXAS265620 isn't in AS265620:AS-UFMX (LACNIC) once expanded. Add AS265620 to it.

Route objects not announced

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

38.65.176.0/21RADBNo ROA
38.65.184.0/21RADBNo ROA
38.94.80.0/20RADBNo ROA
45.189.60.0/22LACNIC, RADBValid

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.