bgpreport

Network · data from 2026-11-12

AS265608 AS265608 - ONT NETWORKS SA de CV

Registry name: AS265608 - ONT NETWORKS SA de CV, MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265608, 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.234.161.0/24 No ROA None 2 0%low visibility 2
45.188.79.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
45.188.76.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
45.188.77.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
45.188.78.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
2806:365:c000::/35 Valid RIR databaseLACNIC, RADB 635 100% 69
2806:365::/33 Valid RIR databaseLACNIC, RADB 634 100% 69
2806:365:8000::/34 Valid RIR databaseLACNIC 633 100% 69

AS-SET

AS265608 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 5 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none201.234.161.0/24No ROA covers it. Add a ROA for AS265608, maxLength 24.2 of 673
Route object: none201.234.161.0/24No route object for it. Add a route object with origin AS265608 in the RIR database for the space.2 of 673

Route objects not announced

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

45.188.76.0/22RADBNo ROA
2806:365:8000::/33RADBNo ROA
2806:365:e000::/35LACNIC, 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.