bgpreport

Network · data from 2026-11-12

AS272988 HSEIngenieria SAS

Registry name: AS272988 - Hydra Soluciones Empresariales Ingenieria SAS, CO · PeeringDB

5IPv4 routes 80.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.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
2Route objects not announced registered with origin AS272988, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272988, 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.
38.210.226.0/24 No ROA Other IRR onlyRADB 639 95% 67
185.240.89.0/24 Valid RIR databaseRIPE 672 100% 67
2.152.33.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
185.236.182.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
185.240.88.0/24 Valid RIR databaseRIPE 668 99% 67
2803:8d90::/32 Valid RIR databaseLACNIC, RADB 631 99% 69

AS-SET

AS272988'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 4 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.210.226.0/24No ROA covers it. Add a ROA for AS272988, maxLength 24.639 of 673
Route object: RIR38.210.226.0/24Route object only in RADB. Add it in the RIR database for the space.639 of 673

Route objects not announced

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

185.240.88.0/23RIPEValid
2803:7430::/32RADBNo 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.