BGP Communities

BGP Routing Policy AS7195


EdgeUno is an Internet Service Provider and Managed Services company that provides infrastructure at national or global scale.  

This document provides information about our routing policy, and how customers can control their prefixes inside our network.   

EdgeUno have a selective peering policy, and our network information can be found updated at   

Local Preference   

By default, all received customer routes are assigned a local preference of 300 in Edgeuno Backbone. Customer can change this preference using the following BGP communities:  

Community  Local Preference  Effect 
7195:290  290  Used to customer backup when multihomed to Edgeuno Backbone  
7195:200  200  Set preference equal to peer routes  
7195:100  100  Set preference equal to transit routes 

Traffic Engineering  

The use of this communities allow customer to prevent their prefixes from being advertised to specific peers or prepend their routes to a subset of peers.  

Not all our peers are eligible to traffic engineering. Bellow we have a table with a list of peers and transit connections that accept this manipulation.  

Traffic engineering communities are formatted   AAYZZ : ASN   where:   


AA   Private code and will be always 64.   

Y   Action code where:  

0 – Suppress the announce  

1 – Prepends 1 AS-SET inside Edgeuno backbone  

2 – Prepends 2 AS-SET inside Edgeuno backbone  

3 – Prepends 3 AS-SET inside Edgeuno backbone  


ZZ  Country Code where:  

01 – USA  

51 – Peru  

52 – Mexico  

54 – Argentina   

55 – Brazil   

56 – Chile  

57 – Colombia   

90  Turkey 

Example:   64055:6762 will suppress the announce of tagged prefix to AS6762 (Sparkle) in Brazil.  

                    64357:3549 will add three as-path prepends in prefixes announced to CenturyLink in Colombia   


Edgeuno ASN Peers eligible to traffic engineering:  

ASN  Country  Role 
63000  N/A   All Transit Connections in the country where it is used. 
65000  N/A   All Peering Connections in the country where it is used. 
65001  USA   FL-IX  
65002  USA   NOTA 
65003  USA   DE-CIX NYC 
65004  USA   NYIIX 
65005  USA   Equinix NYC 
65006  USA   Equinix Ashburn 
60068  USA   CDN77 Peering  
13786  USA   Seaborn 
6762  USA   Transit – Sparkle  
174  USA   Transit – Cogent  
65001  Argentina   CABASE 
6762  Argentina   Transit – Sparkle   
3356  Argentina   Transit – Level 3  
65004  Brazil   IX.BR Rio de Janeiro 
65003  Brazil   IX.BR Sao Paulo 
65002  Brazil   Equinix Sao Paulo IX 
65001  Brazil   IX.BR ALL 
22356  Brazil   Transit – Durand   
13786  Brazil   Transit – Seaborn  
6762  Brazil   Transit – Sparkle 
3549  Brazil   Transit 3459 Lumen  
3356  Brazil   Transit 3356 Lumen 
7738  Brazil  Oi 
65100  Chile   Private Peer PIT Chile 
65001  Chile   All Peers PIT Chile 
6762  Chile   Transit – Sparkle   
3356  Chile   Transit – Lumen 
27901   Chile  Mundo Pacifico 
22047  Chile  VTR 
65002  Colombia   Equinix IX 
65001  Colombia   NAP Colombia 
6762  Colombia   Transit – Sparkle   
3549  Colombia   Transit – Lumen 
65001  Mexico  Transtelco 
65002  Mexico  Totalplay 
14178  Mexico  Megacable 
1299  Mexico  Telia 
174  Mexico  Cogent 
3549   Peru  Lumen 
65001  Peru  Pit Peru 
65002  Turkey  DE-CIX Frankfurt 
65003  Turkey  Turk Telekom International Transit 
6663  Turkey  Turk Telekom Turkey Access 
34984  Turkey  Turkcell/Superonline 
12735  Turkey  Turknet  


Third Parties 

Where available, we have set peering sessions with the following third parties for which the traffic engineering communities are also offered.  

ASN   Role  
15169  Google 
8075  Microsoft 
16509  Amazon 
7160  Oracle 



Customer can use special community 7195:666 to discard traffic destined to hosts inside Edgeuno (and transit partners). Only /32 and /128 masks are accepted for the use of this community and only for prefix-range already configured in customer prefix-list.   

Community  Effect 
7195:666  Blackhole Traffic