AS268829

// JARAGUA TECNOLOGIA EM TELECOMUNICACOES // Zuttel

📊 ASN Categories: 🌐 ISP

aut-num: AS268829
as-name: ZUTTEL
descr: ZUTTEL FIBRA
import: from AS53062 accept ANY
import: from AS263998 accept ANY
import: from AS53013 accept ANY
mp-import: afi ipv6.unicast from AS53062 accept ANY
mp-import: afi ipv6.unicast from AS263998 accept ANY
mp-import: afi ipv6.unicast from AS53013 accept ANY
export: to AS53062 announce AS268829:AS-ZUTTEL-ALL
export: to AS263998 announce AS268829:AS-ZUTTEL-ALL
export: to AS53013 announce AS268829:AS-ZUTTEL-ALL
mp-export: afi ipv6.unicast to AS53062 announce AS268829:AS-ZUTTEL-ALL
mp-export: afi ipv6.unicast to AS263998 announce AS268829:AS-ZUTTEL-ALL
mp-export: afi ipv6.unicast to AS53013 announce AS268829:AS-ZUTTEL-ALL
admin-c: RAFAEL-LEITE-ZUTTEL
tech-c: vicente-nicolas
remarks: =============================================== 24 x 7 technical support regarding our BGP routing policies or any inquiries concerning AS268829's security and routing policies please reach out to us at the following channels:
remarks: ============================================================ AS268829 Basic Interconnection Requirements ============================================================
remarks: ============================================================ The following is required from your organization in order to establish a BGP session with ZUTTEL at ASN 268829: - 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: ZUTTEL 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! ============================================================
mnt-by: MAINT-AS268829
changed: rafael@zuttel.com.br 20250613 # 18:19 GMT
source: RADB
last-modified: 2025-06-13T18:19:52Z 

MM AS-53062-CUSTOMERSMM AS-OPENX-CUSTOMERSMM AS-MMTELECOMMM AS-HUGENET-CUSTOMERSMM AS-UFINET-LATAM-BRASILMM AS-CTBC-CUSTOMERS156MM AS-ITXBRMM AS-8167-BGP-CUSTOMERSMM AS-ULTRATELECOM-BRMM AS-267613MM AS-CTBC-TOOLSMM AS-8167_CUSTOMERSMM AS-HURRICANEV6

MM AS-53062-CUSTOMERS
MM AS-OPENX-CUSTOMERS
MM AS-MMTELECOM
MM AS-HUGENET-CUSTOMERS
MM AS-UFINET-LATAM-BRASIL
MM AS-CTBC-CUSTOMERS156
MM AS-ITXBR
MM AS-8167-BGP-CUSTOMERS
MM AS-ULTRATELECOM-BR
MM AS-267613
MM AS-CTBC-TOOLS
MM AS-8167_CUSTOMERS
MM AS-HURRICANEV6
#0 1
members: 0
members: 1
M AS268829