bgpreport

Network · data from 2026-11-12

AS270114 270114

Registry name: AS270114 - SERVICIOS DE INFRAESTRUCTURA DE RADIOCOMUNICACION Y REDES PRIVADAS DE DATOS HYPERNET, SC DE RL DE CV, MX · PeeringDB

4IPv4 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
34Route objects not announced registered with origin AS270114, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270114, 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.

2806:3b5::/32 No ROA Other IRR onlyRADB 635 100% 69
187.102.236.0/24 Valid Other IRR onlyRADB 672 100% 67
187.102.238.0/24 Valid Other IRR onlyRADB 672 100% 67
187.102.239.0/24 Valid Other IRR onlyRADB 672 100% 67
187.102.236.0/22 Valid RIR databaseLACNIC, RADB 672 100% 67

AS-SET

AS270114'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 39 are in fix.csv.

  • ROA: none1
  • Route object: RIR4
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: none2806:3b5::/32No ROA covers it. Add a ROA for AS270114, maxLength 32.635 of 636
Route object: RIR2806:3b5::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR187.102.236.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.102.238.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.102.239.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

187.102.236.0/23RADBValid
187.102.237.0/24RADBValid
187.102.238.0/23RADBValid
2806:3b5::/36RADBNo ROA
2806:3b5::/48RADBNo ROA
2806:3b5:1::/48RADBNo ROA
2806:3b5:2::/48RADBNo ROA
2806:3b5:3::/48RADBNo ROA
2806:3b5:4::/48RADBNo ROA
2806:3b5:5::/48RADBNo ROA
2806:3b5:6::/48RADBNo ROA
2806:3b5:7::/48RADBNo ROA
2806:3b5:8::/48RADBNo ROA
2806:3b5:9::/48RADBNo ROA
2806:3b5:a::/48RADBNo ROA
2806:3b5:b::/48RADBNo ROA
2806:3b5:c::/48RADBNo ROA
2806:3b5:d::/48RADBNo ROA
2806:3b5:e::/48RADBNo ROA
2806:3b5:f::/48RADBNo ROA
2806:3b5:10::/48RADBNo ROA
2806:3b5:11::/48RADBNo ROA
2806:3b5:12::/48RADBNo ROA
2806:3b5:13::/48RADBNo ROA
2806:3b5:14::/48RADBNo ROA
2806:3b5:15::/48RADBNo ROA
2806:3b5:16::/48RADBNo ROA
2806:3b5:17::/48RADBNo ROA
2806:3b5:18::/48RADBNo ROA
2806:3b5:19::/48RADBNo ROA
2806:3b5:1a::/48RADBNo ROA
2806:3b5:1b::/48RADBNo ROA
2806:3b5:1c::/48RADBNo ROA
2806:3b5:1d::/48RADBNo ROA

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.