bgpreport

Network · data from 2026-11-12

AS28475 AS28475 - Fomento Economico Mexicano S. A. de C. V.

Registry name: AS28475 - Fomento Economico Mexicano S. A. de C. V., MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28475, 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.
200.23.217.128/27 No ROA Nonecovered by 200.23.217.0/24 1 0%low visibility 1
200.13.40.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1
200.23.23.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1
200.23.212.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1
200.23.213.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1
200.23.214.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1
200.23.218.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1
200.23.219.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1
200.23.220.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1
200.23.221.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1

AS-SET

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

  • ROA: none10
  • Route object: none1
  • Route object: RIR9
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none200.23.217.128/27No ROA covers it. Add a ROA for AS28475, maxLength 27.1 of 673
Route object: none200.23.217.128/27No route object for it. A route object for 200.23.217.0/24 with origin AS28475 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS28475 in the RIR database for the space.1 of 673
ROA: none200.13.40.0/24No ROA covers it. Add a ROA for AS28475, maxLength 24.2 of 673
Route object: RIR200.13.40.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none200.23.23.0/24No ROA covers it. Add a ROA for AS28475, maxLength 24.2 of 673
Route object: RIR200.23.23.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none200.23.212.0/24No ROA covers it. Add a ROA for AS28475, maxLength 24.2 of 673
Route object: RIR200.23.212.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none200.23.213.0/24No ROA covers it. Add a ROA for AS28475, maxLength 24.2 of 673
Route object: RIR200.23.213.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none200.23.214.0/24No ROA covers it. Add a ROA for AS28475, maxLength 24.2 of 673
Route object: RIR200.23.214.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none200.23.218.0/24No ROA covers it. Add a ROA for AS28475, maxLength 24.2 of 673
Route object: RIR200.23.218.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none200.23.219.0/24No ROA covers it. Add a ROA for AS28475, maxLength 24.2 of 673
Route object: RIR200.23.219.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none200.23.220.0/24No ROA covers it. Add a ROA for AS28475, maxLength 24.2 of 673
Route object: RIR200.23.220.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none200.23.221.0/24No ROA covers it. Add a ROA for AS28475, maxLength 24.2 of 673
Route object: RIR200.23.221.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

200.23.216.0/24RADBNo ROA
200.23.217.0/24RADBNo ROA

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.