aut-num:        AS263324
as-name:        UNSPECIFIED
descr:          Net&Com Serviços de Informática e Telecomunicações
admin-c:        NEINT4-NICBR
tech-c:         NEINT4-NICBR
mnt-by:         MAINT-AS263324
notify:         [email protected]
changed:        [email protected] 20151203  #00:53:09(BRST)
source:         TC

aut-num:        AS263324
as-name:        NETECOM
descr:          Netecom Internet
import:         from AS28329   accept ANY
import:         from AS28260   accept ANY
import:         from AS28210   accept ANY
mp-import:      afi ipv6.unicast from AS28329   accept ANY
mp-import:      afi ipv6.unicast from AS28260   accept ANY
mp-import:      afi ipv6.unicast from AS28210   accept ANY
export:         to AS28260   announce AS263324:AS-NETECOM-ALL
export:         to AS28210   announce AS263324:AS-NETECOM-ALL
export:         to AS28329   announce AS263324:AS-NETECOM-ALL
mp-export:      afi ipv6.unicast to AS28260   announce AS263324:AS-NETECOM-ALL
mp-export:      afi ipv6.unicast to AS28210   announce AS263324:AS-NETECOM-ALL
mp-export:      afi ipv6.unicast to AS28329   announce AS263324:AS-NETECOM-ALL
admin-c:        Rodrigo O. Gomes
tech-c:         Rudson Costa
remarks:        ===============================================
                NET&COM
                Website: https://www.netecomcorp.com.br/
                Status Page: http://status.netecom.com.br/
                Looking Glass: http://lg.netecom.net.br/
                BGP View: http://bgpview.netecom.com.br:3000/
                Routing Policy and Communities: http://www.netecom.com.br/routingpolicy
                ===============================================
remarks:        ===============================================
                24 x 7 technical support regarding our BGP routing
                policies or any inquiries concerning AS263324's
                security and routing policies please reach out to us
                at the following channels:
remarks:        Network issues / requests: [email protected]
                Peering issues / requests: [email protected]
                Abuse and SPAM : [email protected]
                Or dial +55 (21) 3030-4600
                ===============================================
remarks:        ============================================================
                AS263324 Basic Interconnection Requirements
                ============================================================
remarks:        The following is required from your organization in order to
                establish a BGP session with Net&Com at ASN 263324:
                - 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:        Net&Com 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-AS263324
changed:        [email protected] 20230209  #15:03:47Z
source:         RADB
last-modified:  2025-03-17T15:00:07Z




--- ARIN Whois ---


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


No match found for a AS263324.


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#