bgpreport

Network · data from 2026-11-12

AS2549 Universidad de Guadalajara

Registry name: AS2549 - Universidad de Guadalajara, MX · PeeringDB

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

Announced routes

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

148.202.192.0/18 Valid Nonecovered by 148.202.0.0/16 672 100% 67
207.249.240.0/21 Valid Nonecovered by 207.249.224.0/19 672 100% 67
148.202.0.0/18 Valid Nonecovered by 148.202.0.0/16 671 100% 67
148.202.64.0/18 Valid Nonecovered by 148.202.0.0/16 671 100% 67
148.202.128.0/18 Valid Nonecovered by 148.202.0.0/16 671 100% 67
200.39.160.0/21 Valid Nonecovered by 200.39.160.0/19 671 100% 67
207.249.224.0/21 Valid Nonecovered by 207.249.224.0/19 671 100% 67
207.249.248.0/21 Valid Nonecovered by 207.249.224.0/19 671 100% 67
200.39.168.0/21 Valid Nonecovered by 200.39.160.0/19 670 100% 67
200.39.176.0/21 Valid Nonecovered by 200.39.160.0/19 670 100% 67
200.39.184.0/21 Valid Nonecovered by 200.39.160.0/19 670 100% 67
207.249.232.0/21 Valid Nonecovered by 207.249.224.0/19 668 99% 67
2001:1210:5000::/36 Valid Nonecovered by 2001:1210::/32 636 100% 67
2001:1210::/36 Valid Nonecovered by 2001:1210::/32 634 100% 67
2001:1210:1000::/36 Valid Nonecovered by 2001:1210::/32 634 100% 67
2001:1210:3000::/36 Valid Nonecovered by 2001:1210::/32 605 95% 67
148.202.0.0/16 Valid RIR databaseLACNIC, RADB 671 100% 67
207.249.224.0/19 Valid RIR databaseLACNIC, RADB 671 100% 67
200.39.160.0/19 Valid RIR databaseLACNIC, RADB 670 100% 67
2001:1210::/32 Valid RIR databaseALTDB, LACNIC, RADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS2549: LACNIC::AS-2549. 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 (AS2549 isn't in the set, or no route object for AS2549 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 objectsAS2549 in itNot covered
LACNIC::AS-2549 In no IRR database read today.

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

  • Route object: none16
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none148.202.192.0/18No route object for it. A route object for 148.202.0.0/16 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.672 of 673
Route object: none207.249.240.0/21No route object for it. A route object for 207.249.224.0/19 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.672 of 673
Route object: none148.202.0.0/18No route object for it. A route object for 148.202.0.0/16 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.671 of 673
Route object: none148.202.64.0/18No route object for it. A route object for 148.202.0.0/16 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.671 of 673
Route object: none148.202.128.0/18No route object for it. A route object for 148.202.0.0/16 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.671 of 673
Route object: none200.39.160.0/21No route object for it. A route object for 200.39.160.0/19 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.671 of 673
Route object: none207.249.224.0/21No route object for it. A route object for 207.249.224.0/19 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.671 of 673
Route object: none207.249.248.0/21No route object for it. A route object for 207.249.224.0/19 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.671 of 673
Route object: none200.39.168.0/21No route object for it. A route object for 200.39.160.0/19 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.670 of 673
Route object: none200.39.176.0/21No route object for it. A route object for 200.39.160.0/19 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.670 of 673
Route object: none200.39.184.0/21No route object for it. A route object for 200.39.160.0/19 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.670 of 673
Route object: none207.249.232.0/21No route object for it. A route object for 207.249.224.0/19 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.668 of 673
Route object: none2001:1210:5000::/36No route object for it. A route object for 2001:1210::/32 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.636 of 636
Route object: none2001:1210::/36No route object for it. A route object for 2001:1210::/32 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.634 of 636
Route object: none2001:1210:1000::/36No route object for it. A route object for 2001:1210::/32 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.634 of 636
Route object: none2001:1210:3000::/36No route object for it. A route object for 2001:1210::/32 with origin AS2549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2549 in the RIR database for the space.605 of 636
AS-SET: not foundLACNIC::AS-2549PeeringDB names LACNIC::AS-2549; no IRR database read has it.

Route objects not announced

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