bgpreport

Network · data from 2026-11-12

AS28498 entidades-mo

Registry name: AS28498 - Network Information Center Mexico, MX · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28498, 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.1.0/24 Valid RIR databaseLACNIC, NTTCOM, RADB 672 100% 67
200.94.176.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
2001:13c7:7000::/48 Valid RIR databaseLACNIC, RADB 633 100% 67
2001:1201::/48 Valid RIR databaseLACNIC, RADB 631 99% 69

AS-SET

AS28498'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 8 are in fix.csv.

  • Route object: not announced8

Route objects not announced

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

200.23.0.0/23RADBNo ROA
200.23.0.0/24RADBNo ROA
200.94.176.0/22RADBNo ROA
200.94.176.0/23RADBNo ROA
200.94.177.0/24RADBNo ROA
200.94.178.0/24RADBNo ROA
200.94.179.0/24RADBNo ROA
2001:1201::/44LACNIC, RADBValid

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.