bgpreport

Network · data from 2026-11-12

AS269872 GRUPO MKE

Registry name: AS269872 - GRUPO MKE SAS, AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269872, 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.189.200.0/23 Valid Nonecovered by 45.189.200.0/22 669 99% 66
45.189.202.0/23 Valid Nonecovered by 45.189.200.0/22 668 99% 66
45.189.200.0/24 Valid Nonecovered by 45.189.200.0/22 4 1%low visibility 3
45.189.201.0/24 Valid Nonecovered by 45.189.200.0/22 4 1%low visibility 3
45.189.202.0/24 Valid Nonecovered by 45.189.200.0/22 4 1%low visibility 3
45.189.203.0/24 Valid Nonecovered by 45.189.200.0/22 4 1%low visibility 3
2803:28e0::/48 Valid Nonecovered by 2803:28e0::/32 4 1%low visibility 3
2803:28e0:fe00::/39 Valid Nonecovered by 2803:28e0::/32 4 1%low visibility 3
2803:28e0:fe00::/40 Valid Nonecovered by 2803:28e0::/32 4 1%low visibility 3
2803:28e0:ff00::/40 Valid Nonecovered by 2803:28e0::/32 4 1%low visibility 3
45.189.200.0/22 Valid RIR databaseLACNIC, RADB 670 100% 66
2803:28e0::/32 Valid RIR databaseLACNIC 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS269872: AS269872:AS-GRUPOMKE. 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 (AS269872 isn't in the set, or no route object for AS269872 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 objectsAS269872 in itNot covered
AS269872:AS-GRUPOMKE LACNIC 112 Yes 0

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

  • Route object: none10
ChangePrefix or setDetailFull-table peers
Route object: none45.189.200.0/23No route object for it. A route object for 45.189.200.0/22 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.669 of 673
Route object: none45.189.202.0/23No route object for it. A route object for 45.189.200.0/22 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.668 of 673
Route object: none45.189.200.0/24No route object for it. A route object for 45.189.200.0/22 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.4 of 673
Route object: none45.189.201.0/24No route object for it. A route object for 45.189.200.0/22 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.4 of 673
Route object: none45.189.202.0/24No route object for it. A route object for 45.189.200.0/22 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.4 of 673
Route object: none45.189.203.0/24No route object for it. A route object for 45.189.200.0/22 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.4 of 673
Route object: none2803:28e0::/48No route object for it. A route object for 2803:28e0::/32 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.4 of 636
Route object: none2803:28e0:fe00::/39No route object for it. A route object for 2803:28e0::/32 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.4 of 636
Route object: none2803:28e0:fe00::/40No route object for it. A route object for 2803:28e0::/32 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.4 of 636
Route object: none2803:28e0:ff00::/40No route object for it. A route object for 2803:28e0::/32 with origin AS269872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269872 in the RIR database for the space.4 of 636

Route objects not announced

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