bgpreport

Network · data from 2026-11-12

AS274059 274059

Registry name: AS274059 - K.G.B. TELECOMUNICACIONES S.A.S, CO · PeeringDB

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

Announced routes

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

2803:1a50:40::/42 Valid Nonecovered by 2803:1a50::/32 633 100% 68
138.117.40.0/24 Valid RIR databaseLACNIC 673 100% 67
138.117.42.0/24 Valid RIR databaseLACNIC 672 100% 67
138.117.43.0/24 Valid RIR databaseLACNIC 672 100% 67
2803:1a50:80::/48 Valid RIR databaseLACNIC 634 100% 67
2803:1a50:c0::/42 Valid RIR databaseLACNIC 634 100% 67

AS-SET

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

  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none2803:1a50:40::/42No route object for it. A route object for 2803:1a50::/32 with origin AS274059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274059 in the RIR database for the space.633 of 636

Route objects not announced

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

38.236.181.0/24RADBNo ROA
138.117.40.0/22LACNICValid
170.254.0.0/22LACNICValid
204.157.245.0/24RADBNo ROA
2803:1a50::/32LACNICValid
2803:1a50:40::/48LACNICValid

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.