bgpreport

Network · data from 2026-11-12

AS27695 AS27695 - UNE EPM TELECOMUNICACIONES S.A.

Registry name: AS27695 - UNE EPM TELECOMUNICACIONES S.A., CO · not in PeeringDB

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

Announced routes

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

190.3.224.0/19 Invalid: origin None 4 1%low visibility 4
190.109.128.0/19 Invalid: origin None 4 1%low visibility 4
2800:580:2000:a::/64 Invalid: maxLength Nonecovered by 2800:580::/32 6 1%low visibility 6
2803:cae0:8080::/48 No ROA Other origin only 635 100% 67
2800:580:2000::/35 Valid Nonecovered by 2800:580::/32 636 100% 67
2800:580:2400::/48 Valid Nonecovered by 2800:580::/32 636 100% 67
2800:ea:8000::/36 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS27695 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 18 are in fix.csv.

  • ROA: origin2
  • ROA: maxLength1
  • ROA: none1
  • Route object: none6
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin190.3.224.0/19ROAs covering it name AS13489, not AS27695. If AS27695 should announce it, add a ROA for AS27695.4 of 673
Route object: none190.3.224.0/19No route object for it. Add a route object with origin AS27695 in the RIR database for the space.4 of 673
ROA: origin190.109.128.0/19ROAs covering it name AS13489, not AS27695. If AS27695 should announce it, add a ROA for AS27695.4 of 673
Route object: none190.109.128.0/19No route object for it. Add a route object with origin AS27695 in the RIR database for the space.4 of 673
ROA: maxLength2800:580:2000:a::/64ROA 2800:580::/32 AS27695 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2800:580:2000:a::/64.6 of 636
Route object: none2800:580:2000:a::/64No route object for it. A route object for 2800:580::/32 with origin AS27695 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS27695 in the RIR database for the space.6 of 636
ROA: none2803:cae0:8080::/48No ROA covers it. Add a ROA for AS27695, maxLength 48.635 of 636
Route object: none2803:cae0:8080::/48Route objects for it name AS270046. Add a route object with origin AS27695 in the RIR database for the space.635 of 636
Route object: none2800:580:2000::/35No route object for it. A route object for 2800:580::/32 with origin AS27695 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27695 in the RIR database for the space.636 of 636
Route object: none2800:580:2400::/48No route object for it. A route object for 2800:580::/32 with origin AS27695 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27695 in the RIR database for the space.636 of 636

Route objects not announced

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

138.97.56.0/22LACNIC, RADBValid
181.232.0.0/17LACNICValid
186.43.0.0/17LACNIC, RADBValid
186.159.0.0/18LACNIC, RADBValid
186.159.64.0/19LACNIC, RADBValid
191.103.128.0/17LACNICValid
2800:580::/32LACNICValid
2800:580::/36RADBValid

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.