bgpreport

Network · data from 2026-11-12

AS21692 AS21692 - SECRETARIA ANTICORRUPCION Y BUEN GOBIERNO

Registry name: AS21692 - SECRETARIA ANTICORRUPCION Y BUEN GOBIERNO, MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21692, 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.
2801:c4:1d:100::/56 No ROA Nonecovered by 2801:c4:1d::/48 1 0%low visibility 1
2801:c4:1d:300::/56 No ROA Nonecovered by 2801:c4:1d::/48 1 0%low visibility 1
2801:c4:1d:400::/56 No ROA Nonecovered by 2801:c4:1d::/48 1 0%low visibility 1
2801:c4:1d:1600::/56 No ROA Nonecovered by 2801:c4:1d::/48 1 0%low visibility 1
2801:c4:1d:cafe::/64 No ROA Nonecovered by 2801:c4:1d::/48 1 0%low visibility 1
200.33.31.0/24 No ROA Other IRR onlyRADB 672 100% 67
200.34.175.0/24 No ROA Other IRR onlyRADB 672 100% 67
2801:c4:1d::/48 No ROA Other IRR onlyRADB 635 100% 70

AS-SET

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

  • ROA: none8
  • Route object: none5
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none2801:c4:1d:100::/56No ROA covers it. Add a ROA for AS21692, maxLength 56.1 of 636
Route object: none2801:c4:1d:100::/56No route object for it. A route object for 2801:c4:1d::/48 with origin AS21692 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS21692 in the RIR database for the space.1 of 636
ROA: none2801:c4:1d:300::/56No ROA covers it. Add a ROA for AS21692, maxLength 56.1 of 636
Route object: none2801:c4:1d:300::/56No route object for it. A route object for 2801:c4:1d::/48 with origin AS21692 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS21692 in the RIR database for the space.1 of 636
ROA: none2801:c4:1d:400::/56No ROA covers it. Add a ROA for AS21692, maxLength 56.1 of 636
Route object: none2801:c4:1d:400::/56No route object for it. A route object for 2801:c4:1d::/48 with origin AS21692 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS21692 in the RIR database for the space.1 of 636
ROA: none2801:c4:1d:1600::/56No ROA covers it. Add a ROA for AS21692, maxLength 56.1 of 636
Route object: none2801:c4:1d:1600::/56No route object for it. A route object for 2801:c4:1d::/48 with origin AS21692 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS21692 in the RIR database for the space.1 of 636
ROA: none2801:c4:1d:cafe::/64No ROA covers it. Add a ROA for AS21692, maxLength 64.1 of 636
Route object: none2801:c4:1d:cafe::/64No route object for it. A route object for 2801:c4:1d::/48 with origin AS21692 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS21692 in the RIR database for the space.1 of 636
ROA: none200.33.31.0/24No ROA covers it. Add a ROA for AS21692, maxLength 24.672 of 673
Route object: RIR200.33.31.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.34.175.0/24No ROA covers it. Add a ROA for AS21692, maxLength 24.672 of 673
Route object: RIR200.34.175.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2801:c4:1d::/48No ROA covers it. Add a ROA for AS21692, maxLength 48.635 of 636
Route object: RIR2801:c4:1d::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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