AS269571 (TEX) WHOIS Information

Whois

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:        AS269571
as-name:        TEXTELECOM
descr:          TEX TELECOM
import:         from AS26615   accept ANY
import:         from AS14840   accept ANY
import:         from AS263124   accept ANY
export:         to AS26615   announce AS-TEXTELECOM-269571
export:         to AS14840   announce AS-TEXTELECOM-269571
export:         to AS263124   announce AS-TEXTELECOM-269571
admin-c:        ISA44-NICBR
tech-c:         ISA44-NICBR
mnt-by:         MAINT-AS269571
notify:         isaac.alves@textelecom.net
changed:        isaac.alves@textelecom.net 20210129
source:         ALTDB

aut-num:        AS269571
as-name:        TEX_TELECOM
descr:          TEX TELECOM
admin-c:        ISA44-NICBR
tech-c:         RUCRO64-NICBR
import:         from AS263124 accept ANY
import:         from AS61621 accept ANY
mp-import:      afi ipv6.unicast from AS263124 accept ANY
mp-import:      afi ipv6.unicast from AS61621 accept ANY
export:         to AS263124 announce AS269571:AS-TEX-TELECOM-ALL
export:         to AS61621 announce AS269571:AS-TEX-TELECOM-ALL
mp-export:      afi ipv6.unicast to AS263124 announce AS269571:AS-TEX-TELECOM-ALL
mp-export:      afi ipv6.unicast to AS61621 announce AS269571:AS-TEX-TELECOM-ALL
remarks:        ***************************************************************
Abuse/UCE: noc@textelecom.net
Network: noc@textelecom.net
Peering: noc@textelecom.net
Website: https://portal.textelecom.net/index.php
Looking Glass: http://lg.textelecom.net/
Peering and Routing Policy: http://as269571.peeringdb.com/
***************************************************************
***************************************************************
24 x 7 technical support regarding our BGP routing
policies or any inquiries concerning AS269571's
security and routing policies please reach out to us
at the following channels:
Network issues / requests: noc@textelecom.net
Peering issues / requests: noc@textelecom.net
Abuse and SPAM : noc@textelecom.net or
dial +55 (63) 99273-0330
***************************************************************
***************************************************************
AS269571 Basic Interconnection Requirements
***************************************************************
The following is required from your organization in order to
establish a BGP session with TEX TELECOM at ASN 269571:
- 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")
TEX 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.
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. :-)
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-AS269571
changed:        noc@textelecom.net 20260401
source:         TC
last-modified:  2026-04-02T00:48:19Z