bgpreport

Network · data from 2026-11-12

AS28467 AS28467 - OPTICAL LINE TERMINAL SAS DE CV

Registry name: AS28467 - OPTICAL LINE TERMINAL SAS DE CV, MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28467, 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.
2001:1225::/32 No ROA Other IRR onlyRADB 636 100% 69
38.225.44.0/22 Valid RIR databaseARIN 670 100% 68
89.42.71.0/24 Valid RIR databaseRIPE 670 100% 68
89.45.209.0/24 Valid RIR databaseRADB, RIPE 670 100% 68

AS-SET

AS28467 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 2 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2001:1225::/32No ROA covers it. Add a ROA for AS28467, maxLength 32.636 of 636
Route object: RIR2001:1225::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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