AS263324 Net&Com - Whois Information

as-block: AS219548 - AS396075 descr: ASN block not managed by the RIPE NCC remarks: ------------------------------------------------------ remarks: remarks: aut-num objects within this block represent routing remarks: policy published in the RIPE Database remarks: remarks: For registration information, remarks: you can find the whois server to query, or the remarks: IANA registry to query on this web page: remarks: http://www.iana.org/assignments/ipv4-address-space remarks: remarks: You can access databases of other RIR's at: remarks: remarks: AFRINIC (Africa) remarks: http://www.afrinic.net/ whois.afrinic.net remarks: remarks: APNIC (Asia Pacific) remarks: http://www.apnic.net/ whois.apnic.net remarks: remarks: ARIN (Northern America) remarks: http://www.arin.net/ whois.arin.net remarks: remarks: LACNIC (Latin America and the Carribean) remarks: http://www.lacnic.net/ whois.lacnic.net remarks: remarks: ------------------------------------------------------ mnt-by: RIPE-DBM-MNT created: 2026-06-02T14:29:24Z last-modified: 2026-06-02T14:29:24Z source: RIPE remarks: **************************** remarks: * THIS OBJECT IS MODIFIED remarks: * Please note that all data that is generally regarded as personal remarks: * data has been removed from this object. remarks: * To view the original object, please query the RIPE Database at: remarks: * http://www.ripe.net/whois remarks: **************************** aut-num: AS263324 as-name: UNSPECIFIED descr: Net&amp;Com ServiÃ§os de InformÃ¡tica e TelecomunicaÃ§Ãµes admin-c: NEINT4-NICBR tech-c: NEINT4-NICBR mnt-by: MAINT-AS263324 notify: db-admin@bgp.net.br changed: db-admin@bgp.net.br 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&amp;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: noc@netecom.com.br Peering issues / requests: peering@netecom.com.br Abuse and SPAM : abuse@netecom.com.br 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&amp;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 (&quot;IRR as-set/route-set&quot;) remarks: Net&amp;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 &quot;cleaning up your own house first&quot;, 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: noc@netecom.com.br 20230209 #15:03:47Z source: RADB last-modified: 2025-03-17T15:00:07Z

AS263324 (Net&Com)

AS263324 (Net&Com)

AS263324 (Net&Com) WHOIS Information