WWW.ROBTEX.COM - AS267942
Search for IP or hostnames
61+4862
Onlive Telecom LTDA // Primeline Latam LTDA // Onlive Telecom
aut-num: AS267942
as-name: PRIMELINE
descr: =============================== PRIMELINE LATAM TELECOM LTDA ===============================
import: from AS269553 accept ANY
import: from AS264409 accept ANY
mp-import: afi ipv6.unicast from AS269553 accept ANY
mp-import: afi ipv6.unicast from AS264409 accept ANY
export: to AS269553 announce AS267942:AS-PRIMELINE-LATAM-ALL
export: to AS264409 announce AS267942:AS-PRIMELINE-LATAM-ALL
mp-export: afi ipv6.unicast to AS269553 announce AS267942:AS-PRIMELINE-LATAM-ALL
mp-export: afi ipv6.unicast to AS264409 announce AS267942:AS-PRIMELINE-LATAM-ALL
admin-c: ANDRE-SILVA
tech-c: RUDSON-COSTA-3R
remarks: =============================================== Primeline Latam Website: https://onlivetelecom.com Peering and Routing Policy: https://www.peeringdb.com/net/18242 Peering: peering@primelinelatam.com =============================================== =============================================== 24 x 7 technical support regarding our BGP routing policies or any inquiries concerning AS267942's security and routing policies please reach out to us at the following channels: Network issues / requests: engenharia@primelinelatam.com Peering issues / requests: peering@primelinelatam.com Abuse and SPAM : abuse@primelinelatam.com Or dial +55 (21) 2137-8306 =============================================== ============================================================ AS267942 Basic Interconnection Requirements ============================================================ The following is required from your organization in order to establish a BGP session with Primeline Latam at ASN 267942: - The customer must use a RIR assigned ASN. - The customer must have a route/route6 object for each prefix it intends to announce to us, which might include its own prefixes and, if desired, its customers' prefixes as well (customer cone). - Each route/route6 object corresponding to a customer prefix (yours or a prefix from your customer cone) must inform the correct ASN in its 'origin' field. - The ASN mentioned in the 'origin' field of each route and route6 object must have its proper and corresponding aut-num object. - The aforementioned aut-num objects must have a clear routing policy stating what as-sets are to be announced to us. - This as-set MUST be informed on PeeringDB ("IRR as-set/route-set") Primeline Latam strongly encourages you to use two simultaneous methods to validate the origin of the prefixes you announce to us: IRR and ROA (published in your RPKI regime). This is highly recommended because some of our direct upstreams and also indirect upstreams may reject any routes where there is a failure in the origin validation process. You can start this process by "cleaning up your own house first", then working directly with your customers so they can do their homework too, and, by doing that, we can all prevent route leaks and prefix hijacking from happening. :-) Last but not least, please feel free to contact us if you have any questions or need our assistance in working these best practices with you! We will definitely make ourselves available to increase the security of the Internet, your experience as our customer/partner, and in the best interest of our mutual agreement!
notify: notify@primelinelatam.com
mnt-by: MAINT-267942
changed: noc@primelinelatam.com 20240227 # 1710Z
source: RADB
last-modified: 2024-02-27T17:10:49Z
MM AS270874:AS-2MNET-MADEMENEISMIRANDA-PTT-IX-BR-SP
MM AS-7738-BGP-CUSTOMERS
MM AS-SEABORN-CUSTOMER
MM AS-HUGENET-CUSTOMERS
MM AS26615:AS-CUSTOMERS
MM AS-MOB-CUSTOMER-AS61832
MM AS-LINKFULL-CORPORATE
MM AS-E1-AUTOMATION-CUSTOMER
MM AS267942:AS-PRIMELINELATAM
MM AS-FORTEL-CUSTOMERS
#0 1
members: 0
members: 1
M AS267942
dbq