bgpreport

Network · data from 2026-11-12

AS28500 entidades-i

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

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
6Route objects not announced registered with origin AS28500, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS28500, 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.
207.248.68.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
2801:c4:d0::/48 Valid RIR databaseLACNIC, RADB 631 99% 69

AS-SET

AS28500'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 6 are in fix.csv.

  • Route object: not announced6

Route objects not announced

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

207.248.68.0/22RADBNo ROA
207.248.68.0/23RADBNo ROA
207.248.69.0/24RADBNo ROA
207.248.70.0/24RADBNo ROA
207.248.71.0/24RADBNo ROA
2801:c4:d0::/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.