bgpreport

Network · data from 2026-11-12

AS273959 AS273959 - GUECAM TECNOLOGIA Y SERVICIOS E.I.R.L.

Registry name: AS273959 - GUECAM TECNOLOGIA Y SERVICIOS E.I.R.L., PE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273959, 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.226.10.0/24 Valid Nonecovered by 38.226.10.0/23 670 100% 67
38.226.11.0/24 Valid Nonecovered by 38.226.10.0/23 669 99% 67
2803:ff50:400::/40 Valid Nonecovered by 2803:ff50::/32 634 100% 67
2803:ff50:500::/40 Valid Nonecovered by 2803:ff50::/32 634 100% 67
2803:ff50:600::/40 Valid Nonecovered by 2803:ff50::/32 634 100% 67
2803:ff50:100::/40 Valid Other IRR onlyALTDB 631 99% 67
2803:ff50:200::/40 Valid Other IRR onlyALTDB 631 99% 67
2803:ff50:300::/40 Valid Other IRR onlyALTDB 631 99% 67
206.0.28.0/24 Valid RIR databaseALTDB, ARIN 670 100% 67

AS-SET

AS273959 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 10 are in fix.csv.

  • Route object: none5
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none38.226.10.0/24No route object for it. A route object for 38.226.10.0/23 with origin AS273959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273959 in the RIR database for the space.670 of 673
Route object: none38.226.11.0/24No route object for it. A route object for 38.226.10.0/23 with origin AS273959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273959 in the RIR database for the space.669 of 673
Route object: none2803:ff50:400::/40No route object for it. A route object for 2803:ff50::/32 with origin AS273959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273959 in the RIR database for the space.634 of 636
Route object: none2803:ff50:500::/40No route object for it. A route object for 2803:ff50::/32 with origin AS273959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273959 in the RIR database for the space.634 of 636
Route object: none2803:ff50:600::/40No route object for it. A route object for 2803:ff50::/32 with origin AS273959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273959 in the RIR database for the space.634 of 636
Route object: RIR2803:ff50:100::/40Route object only in ALTDB. Add it in the RIR database for the space.631 of 636
Route object: RIR2803:ff50:200::/40Route object only in ALTDB. Add it in the RIR database for the space.631 of 636
Route object: RIR2803:ff50:300::/40Route object only in ALTDB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

38.226.10.0/23ARINValid
2803:ff50::/32LACNIC, RADBValid

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.