bgpreport

Network · data from 2026-11-12

AS273295 AS273295 - Roger Edwin Monzon Mejia

Registry name: AS273295 - Roger Edwin Monzon Mejia, MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273295, 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:1263::/32 No ROA None 636 100% 67
45.133.60.0/23 Valid None 667 99% 68
45.142.42.0/23 Valid RIR databaseRIPE 666 99% 68
85.92.126.0/23 Valid RIR databaseRIPE 666 99% 68

AS-SET

AS273295 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: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2001:1263::/32No ROA covers it. Add a ROA for AS273295, maxLength 32.636 of 636
Route object: none2001:1263::/32No route object for it. Add a route object with origin AS273295 in the RIR database for the space.636 of 636
Route object: none45.133.60.0/23No route object for it. Add a route object with origin AS273295 in the RIR database for the space.667 of 673

Route objects not announced

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

85.92.126.0/24RIPEValid
85.92.127.0/24RIPEValid

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.