aut-num: AS52871
as-name: UNSPECIFIED
descr: TASCOM TELECOMUNICAÇÕES LTDA
admin-c: AJLDC-NICBR
tech-c: AJLDC-NICBR
mnt-by: MAINT-AS52871
source: TC
last-modified: 2025-02-01T21:41:03Z

aut-num: AS52871
as-name: TASCOM
descr: TASCOM
import: from AS6762 accept ANY
import: from AS52863 accept ANY
import: from AS3356 accept ANY
mp-import: afi ipv6.unicast from AS6762 accept ANY
mp-import: afi ipv6.unicast from AS52863 accept ANY
mp-import: afi ipv6.unicast from AS3356 accept ANY
export: to AS6762 announce AS-TASCOM-52871 and AS-TASCOM-CUSTOMERS
export: to AS52863 announce AS-TASCOM-52871 and AS-TASCOM-CUSTOMERS
export: to AS3356 announce AS-TASCOM-52871 and AS-TASCOM-CUSTOMERS
mp-export: afi ipv6.unicast to AS6762 announce AS-TASCOM-52871 and AS-TASCOM-CUSTOMERS
mp-export: afi ipv6.unicast to AS52863 announce AS-TASCOM-52871 and AS52871:AS-CONE
mp-export: afi ipv6.unicast to AS3356 announce AS-TASCOM-52871 and AS-TASCOM-CUSTOMERS
admin-c: Use Telecom BGP Team
tech-c: Use Telecom BGP Team
remarks: ===============================================
USE TELECOM / TASCOM
Website: https://www.usetelecom.com.br
PeeringDB page: http://AS52871.peeringdb.com/
===============================================
remarks: ===============================================
24 x 7 technical support regarding our BGP routing
policies or any inquiries concerning AS52871's
security and routing policies please reach out to us
at the following channels:
remarks: Network issues / requests: noc[at]usetelecom.com.br
Peering issues / requests: peering[at]usetelecom.com.br
Abuse and SPAM : abuse[at]usetelecom.com.br
Or dial +55 (71) 3599-1000
===============================================
remarks: ============================================================
AS52871 Basic Interconnection Requirements
============================================================
remarks: The following is required from your organization in order to
establish a BGP session with Use Telecom / Tascom at ASN 52871:
- 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: Use Telecom 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 valuable customer/partner, and in the best
interest of our mutual agreement!
notify: noc[at]usetelecom.com.br
mnt-by: MAINT-AS52871
changed: noc[at]usetelecom.com.br 20221229 #22:05:53Z
source: RADB
last-modified: 2023-11-13T16:13:28Z

无法连接到whois服务器: whois.lacnic.net 端口: 43