Network · data from 2026-11-12
AS22894 Network Information Center Mexico S.C.
Registry name: AS22894 - Network Information Center Mexico, MX · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22894, 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.
| 201.131.248.0/24 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 201.131.249.0/24 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 201.131.251.0/24 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 207.248.65.0/24 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 200.23.179.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 200.33.111.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 200.34.22.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 200.94.180.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 200.94.181.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 200.94.183.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 200.94.182.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 2001:1250::/44 | Valid | RIR databaseLACNIC, RADB | 636 100% |
| 2001:1250:1000::/44 | Valid | RIR databaseLACNIC, RADB | 636 100% |
| 2001:1250:2000::/44 | Valid | RIR databaseLACNIC, RADB | 636 100% |
| 2001:1250:10::/44 | Valid | RIR databaseLACNIC | 635 100% |
| 2001:1250:3000::/44 | Valid | RIR databaseLACNIC, RADB | 635 100% |
| 2001:1250:d000::/44 | Valid | RIR databaseLACNIC | 635 100% |
| 2001:1250:fff0::/44 | Valid | RIR databaseLACNIC, RADB | 635 100% |
| 2001:1250:ffe0::/44 | Valid | RIR databaseLACNIC, RADB | 634 100% |
| 2001:1250:a000::/44 | Valid | RIR databaseLACNIC, RADB | 251 39% |
| 2001:1250:c000::/44 | Valid | RIR databaseLACNIC, RADB | 251 39% |
| 2001:1250:b000::/44 | Valid | RIR databaseLACNIC, RADB | 246 39% |
| 207.248.64.0/24 | Valid | RIR databaseLACNIC, RADB | 209 31% |
| 201.131.250.0/24 | Valid | RIR databaseLACNIC, RADB | 202 30% |
AS-SET
AS22894's PeeringDB record names no 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 10 are in fix.csv.
- Route object: not announced10
Route objects not announced
Route objects with origin AS22894 whose prefix no peer sees AS22894 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.23.1.0/24 | LACNIC | Valid |
| 200.33.1.0/24 | LACNIC, RADB | Valid |
| 207.248.64.0/23 | RADB | No ROA |
| 2001:1201::/48 | LACNIC | Valid |
| 2001:1250::/32 | RADB | No ROA |
| 2001:1250:e100::/44 | LACNIC, RADB | Valid |
| 2001:1250:e200::/44 | LACNIC, RADB | Valid |
| 2001:1250:e300::/44 | LACNIC, RADB | Valid |
| 2001:1250:ffc0::/44 | LACNIC, RADB | Valid |
| 2801:c4:d0::/48 | LACNIC | Valid |
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.