bgpreport

Network · data from 2026-11-12

AS271805 BMC TECH

Registry name: AS271805 - BMC TECHNOLOGIES SOCIEDAD COMERCIAL DE RESPONSABILIDAD LIMITADA, PE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271805, 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.
179.51.160.0/24 No ROA Nonecovered by 179.51.160.0/22 672 100% 67
179.51.161.0/24 No ROA Nonecovered by 179.51.160.0/22 671 100% 67
179.51.162.0/24 No ROA Nonecovered by 179.51.160.0/22 671 100% 67
179.51.163.0/24 No ROA Nonecovered by 179.51.160.0/22 671 100% 67
2803:efe0::/33 No ROA None 636 100% 67
2803:efe0:8000::/33 No ROA None 636 100% 67

AS-SET

AS271805'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 13 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none179.51.160.0/24No ROA covers it. Add a ROA for AS271805, maxLength 24.672 of 673
Route object: none179.51.160.0/24No route object for it. A route object for 179.51.160.0/22 with origin AS271805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271805 in the RIR database for the space.672 of 673
ROA: none179.51.161.0/24No ROA covers it. Add a ROA for AS271805, maxLength 24.671 of 673
Route object: none179.51.161.0/24No route object for it. A route object for 179.51.160.0/22 with origin AS271805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271805 in the RIR database for the space.671 of 673
ROA: none179.51.162.0/24No ROA covers it. Add a ROA for AS271805, maxLength 24.671 of 673
Route object: none179.51.162.0/24No route object for it. A route object for 179.51.160.0/22 with origin AS271805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271805 in the RIR database for the space.671 of 673
ROA: none179.51.163.0/24No ROA covers it. Add a ROA for AS271805, maxLength 24.671 of 673
Route object: none179.51.163.0/24No route object for it. A route object for 179.51.160.0/22 with origin AS271805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271805 in the RIR database for the space.671 of 673
ROA: none2803:efe0::/33No ROA covers it. Add a ROA for AS271805, maxLength 33.636 of 636
Route object: none2803:efe0::/33No route object for it. Add a route object with origin AS271805 in the RIR database for the space.636 of 636
ROA: none2803:efe0:8000::/33No ROA covers it. Add a ROA for AS271805, maxLength 33.636 of 636
Route object: none2803:efe0:8000::/33No route object for it. Add a route object with origin AS271805 in the RIR database for the space.636 of 636

Route objects not announced

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

179.51.160.0/22RADBNo 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.