AS52995 AS52995 - Whois Information

as-block: AS1 - AS64511 descr: Includes all AS numbers. descr: Required to allow any aut-num to be descr: added to the C4RR database by descr: the maintainers. admin-c: DUMY-RIPE tech-c: DUMY-RIPE notify: eng@canarie.ca mnt-by: CANARIE-MNT changed: unread@ripe.net 20000101 source: CANARIE as-block: AS52224 - AS54443 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: 2022-02-14T15:07:37Z last-modified: 2022-02-14T15:07:37Z 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: AS52995 as-name: UNSPECIFIED descr: TECHNet Informatica Ltda admin-c: SES503-NICBR tech-c: SES503-NICBR mnt-by: MAINT-AS52995 source: TC last-modified: 2025-02-01T21:41:03Z aut-num: AS52995 as-name: TENINTERNET descr: TENINTERNET import: from AS3356 accept ANY import: from AS269595 accept ANY import: from AS61620 accept ANY mp-import: afi ipv6.unicast from AS3356 accept ANY mp-import: afi ipv6.unicast from AS269595 accept ANY mp-import: afi ipv6.unicast from AS61620 accept ANY export: to AS3356 announce AS52995:AS-TENINTERNET-ALL export: to AS269595 announce AS52995:AS-TENINTERNET-ALL export: to AS61620 announce AS52995:AS-TENINTERNET-ALL mp-export: afi ipv6.unicast to AS3356 announce AS52995:AS-TENINTERNET-ALL mp-export: afi ipv6.unicast to AS269595 announce AS52995:AS-TENINTERNET-ALL mp-export: afi ipv6.unicast to AS61620 announce AS52995:AS-TENINTERNET-ALL admin-c: Raimara tech-c: Raimara remarks: *************************************************************** remarks: Abuse/UCE: raimara@teninternet.com.br remarks: Network: raimara@teninternet.com.br remarks: Peering: raimara@teninternet.com.br remarks: Website: https://teninternet.com.br remarks: Peering and Routing Policy: https://asAS52995.peeringdb.com/ remarks: *************************************************************** remarks: 24 x 7 technical support regarding our BGP routing remarks: policies or any inquiries concerning AS52995's remarks: security and routing policies please reach out to us remarks: at the following channels: remarks: Network issues / requests: raimara@teninternet.com.br remarks: Peering issues / requests: raimara@teninternet.com.br remarks: Abuse and SPAM : raimara@teninternet.com.br remarks: dial +55 (74) 9950-1818 remarks: *************************************************************** remarks: AS52995 Basic Interconnection Requirements remarks: *************************************************************** remarks: The following is required from your organization in order to remarks: establish a BGP session with Power Telecom at ASN AS52995: remarks: - The customer must use a RIR assigned ASN. remarks: - The customer must have a route/route6 object for each prefix remarks: it intends to announce to us, which might include its own remarks: prefixes and, if desired, its customers' prefixes as well remarks: (customer cone). remarks: - Each route/route6 object corresponding to a customer prefix remarks: (yours or a prefix from your customer cone) must inform the remarks: correct ASN in its 'origin' field. remarks: - The ASN mentioned in the 'origin' field of each remarks: route and route6 remarks: object must have its proper and corresponding remarks: aut-num object. remarks: - The aforementioned aut-num objects must have a clear routing remarks: policy stating what as-sets are to be announced to us. remarks: - This as-set MUST be informed on PeeringDB remarks: (&quot;IRR as-set/route-set&quot;) remarks: Power Telecom strongly encourages you to use two remarks: simultaneous methods to remarks: validate the origin of the prefixes you announce remarks: to us: IRR and ROA remarks: (published in your RPKI regime). This is highly remarks: recommended because remarks: some of our direct upstreams and also indirect remarks: upstreams may reject remarks: any routes where there is a failure in the origin remarks: validation process. remarks: You can start this process by &quot;cleaning up your remarks: own house first&quot;, then remarks: working directly with your customers so they can remarks: do their homework too, remarks: and, by doing that, we can all prevent route leaks remarks: and prefix hijacking from happening. :-) remarks: Last but not least, please feel free to contact us remarks: if you have any questions remarks: or need our assistance in working these best remarks: practices with you! remarks: We will definitely make ourselves available to remarks: increase the security of the remarks: Internet, your experience as our customer/partner, remarks: and in the best remarks: interest of our mutual agreement! remarks: *************************************************************** mnt-by: MAINT-AS52995 changed: raimara@teninternet.com.br 20260512 # 13:13 GMT source: RADB last-modified: 2026-05-12T13:13:18Z

AS52995 (AS52995)

AS52995 (AS52995)

AS52995 (AS52995) WHOIS Information