bgpreport

Network · data from 2026-11-12

AS270032 AS270032 - MIRANET S.A.C.

Registry name: AS270032 - MIRANET S.A.C., PE · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS270032, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270032, 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.233.44.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
200.233.45.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
200.233.47.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
2803:25e0::/36 Valid RIR databaseLACNIC, RADB 634 100% 69
2803:25e0:1000::/36 Valid RIR databaseLACNIC, RADB 634 100% 69
2803:25e0:2000::/36 Valid RIR databaseLACNIC, RADB 634 100% 69
2803:25e0:4000::/36 Valid RIR databaseLACNIC, RADB 634 100% 69
2803:25e0:3000::/36 Valid RIR databaseLACNIC, RADB 1 0%low visibility 1

AS-SET

AS270032 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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