AS262765:AS-VELLOZNET

as-set: AS262765:AS-VELLOZNET
descr: *********************************************** NET FACIL SISTEMAS ELETRONICOS LTDA (AS262765) own networks only ***********************************************
members: AS262765
admin-c: Pablo Ferretti
tech-c: Rudson Costa
remarks: =============================================== VELLOZNET Website: https://www.velloznet.com.br/ Status Page: http://status.velloznet.com.br/ Looking Glass: http://lg.velloznet.com.br/ BGP View: http://bgpview.velloznet.com.br:3000/ Routing Policy and Communities: http://www.velloznet.com.br/routingpolicy ===============================================
remarks: =============================================== 24 x 7 technical support regarding our BGP routing policies or any inquiries concerning AS262765's security and routing policies please reach out to us at the following channels:
remarks: Network issues / requests: noc@velloznet.com.br Peering issues / requests: peering@velloznet.com.br Abuse and SPAM : abuse@velloznet.com.br Or dial +55 (12) 3152-7787 ===============================================
remarks: ============================================================ AS262765 Basic Interconnection Requirements ============================================================
remarks: The following is required from your organization in order to establish a BGP session with VELLOZNET at ASN 262765: - 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")
remarks: VELLOZNET 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.
remarks: 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. :-)
remarks: 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: cco@velloznet.com.br
mnt-by: MAINT-AS262765
changed: cco@velloznet.com.br 20210712 #20:47:25Z
source: RADB
last-modified: 2025-05-09T14:00:04Z