WWW.ROBTEX.COM - AS53123
Search for IP or hostnames:
// Power Telecomunicações // PowerTelecom
aut-num: AS53123
as-name: POWER-TELECOMUNICACOES
descr: POWER TELECOMUNICACOES
admin-c: PTLME5-NICBR
tech-c: PTLME5-NICBR
member-of: AS-PTTMetro-SP
member-of: AS-PTTMetro-ATM4-SP
member-of: AS-PTTMetro-ATM6-SP
import: from AS61568 accept ANY
import: from AS264479 accept ANY
mp-import: afi ipv6.unicast from AS61568 accept ANY
mp-import: afi ipv6.unicast from AS264479 accept ANY
export: to AS61568 announce AS53123:AS-POWER-TELECOM-ALL
export: to AS264479 announce AS53123:AS-POWER-TELECOM-ALL
mp-export: afi ipv6.unicast to AS61568 announce AS53123:AS-POWER-TELECOM-ALL
mp-export: afi ipv6.unicast to AS264479 announce AS53123:AS-POWER-TELECOM-ALL
remarks: ========================================================== POWER TELECOM (AS53123) Abuse/UCE: noc@powertelecom.net.br Network: noc@powertelecom.net.br Peering: noc@powertelecom.net.br Peering and Routing Policy: http://as53123.peeringdb.com/ Website: https://www.powertelecom.net.br/ ==========================================================
remarks: =============================================== 24 x 7 technical support regarding our BGP routing policies or any inquiries concerning AS53123's security and routing policies please reach out to us at the aforementioned channels:
remarks: ============================================================ AS53123 Basic Interconnection Requirements ============================================================
remarks: The following is required from your organization in order to establish a BGP session with POWER TELECOM at ASN AS53123: - 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: POWER 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 customer/partner, and in the best interest of our mutual agreement!
mnt-by: MAINT-AS53123
changed: noc@powertelecom.net.br 20250219
source: TC
last-modified: 2025-03-18T23:44:00Z
Hostnames in AS
MM AS-MOB-CUSTOMER-AS52720
MM AS14840:AS-CUSTOMERS-04
MM AS-DIVIVOX
MM AS-7738-BGP-CUSTOMERS
MM AS-CTBC-CUSTOMERS3
MM AS53013:AS-CONE
MM AS-HUGENET-CUSTOMERS
MM AS-UFINET-LATAM-BRASIL
MM AS-263880-CUST
MM AS26615:AS-CUSTOMERS
MM AS-TURBOZONE-CUSTOMERS
MM AS61568:AS-ALOO-TELECOM
MM AS-CTBC-CUSTOMERS189
MM AS-TELY
MM AS-MOB-CUSTOMER-AS269719
MM AS-ITXBR1
MM AS-DURAND1-CUSTOMER
MM AS-ITXBR
MM AS-E1-AUTOMATION-CUSTOMER
MM AS-53427-TGLOBAL
MM AS-7738_CUSTOMERS
MM AS52873:AS-TRANSIT
MM AS-CTBC-TOOLS
MM AS-ITSBRASIL-CUSTOMER
MM AS-HWNG-DOWNSTREAMS
MM AS-HURRICANEV6
MM AS-FORTEL-CUSTOMERS
#0 1
members: 0
members: 1
M AS53123
dbq