resource·aut-num
AS269571
registered in = count($srcs) ?> source · 47 route objects originated (14 v4 / 33 v6)
aut-num objects
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 [at] textelecom [dot] net
Network: noc [at] textelecom [dot] net
Peering: noc [at] textelecom [dot] 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 [at] textelecom [dot] net
Peering issues / requests: noc [at] textelecom [dot] net
Abuse and SPAM : noc [at] textelecom [dot] 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 [at] textelecom [dot] net 20260401
source: TC
last-modified: 2026-04-02T00:48:19Z
originated prefixes 47 route objects
member of sets
AS265023:AS-ALL ALTDB
AS-267613 RADB
AS-53427-TGLOBAL RADB
AS-53427-TGN RADB
AS-BRISANET-CUSTOMERS RADB
AS-CTBC-CUSTOMERS196 RADB
AS-CTBC-TOOLS-3 RADB
AS-DURAND1-CUSTOMER RADB
AS-ELETRONET-CUST RADB
AS-EMBRATELNET RADB
AS-EVRD-CUSTOMER RADB
AS-FLYS RADB
AS-FORTEL-CUSTOMERS RADB
AS-MOB-CUSTOMER-AS53237 RADB
AS-SAMM RADB
AS-SB-AUTOMATION-CUSTOMER RADB
AS-UFINET-LATAM-BRASIL RADB
AS14840:AS-CUSTOMERS-01 RADB
AS53013:AS-CONE RADB
AS61568:AS-ALOO-TELECOM-DDOS RADB
AS-TECTURBO-269571 TC
AS269571:AS-TEX-TELECOM TC
AS270664:AS-CUSTOMERS TC
AS270735:AS-CUSTOMERS TC
AS52573:AS-CUSTOMERS TC
AS52573:AS-CUSTOMERS2 TC
AS61595:AS-DOWNSTREANS TC
change history aut-num + all its route objects, newest first
| time (UTC) | op | class | object | source | serial |
|---|---|---|---|---|---|
| 2024-12-07 00:00:00 | new | route | 45.188.52.0/23AS269571 ⧉ | RADB | 5380431 |
| 2023-12-01 00:00:00 | mod | route | 45.188.55.0/24AS269571 ⧉ | RADB | 4232386 |
| 2023-12-01 00:00:00 | mod | route | 45.188.54.0/24AS269571 ⧉ | RADB | 4232385 |
| 2023-12-01 00:00:00 | mod | route | 45.188.54.0/23AS269571 ⧉ | RADB | 4232384 |
| 2023-12-01 00:00:00 | mod | route | 45.188.53.0/24AS269571 ⧉ | RADB | 4232383 |
| 2023-12-01 00:00:00 | mod | route | 45.188.52.0/24AS269571 ⧉ | RADB | 4232382 |
| 2023-12-01 00:00:00 | mod | route | 45.188.52.0/22AS269571 ⧉ | RADB | 4232381 |
| 2023-12-01 00:00:00 | mod | route6 | 2804:669c::/41AS269571 ⧉ | RADB | 3169700 |
| 2023-12-01 00:00:00 | mod | route6 | 2804:669c::/32AS269571 ⧉ | RADB | 3169699 |
| 2022-01-01 00:00:00 | new | route6 | 2804:669c::/41AS269571 ⧉ | RADB | 2385704 |
| 2021-10-01 00:00:00 | new | route | 45.188.52.0/24AS269571 ⧉ | RADB | 2332476 |
| 2021-05-01 00:00:00 | new | route | 45.188.55.0/24AS269571 ⧉ | RADB | 2107719 |
| 2021-05-01 00:00:00 | new | route | 45.188.54.0/24AS269571 ⧉ | RADB | 2107718 |
| 2021-05-01 00:00:00 | new | route | 45.188.54.0/23AS269571 ⧉ | RADB | 2107717 |
| 2021-05-01 00:00:00 | new | route | 45.188.53.0/24AS269571 ⧉ | RADB | 2107716 |
| 2019-12-01 00:00:00 | new | route | 45.188.52.0/22AS269571 ⧉ | RADB | 1714571 |
| 2019-12-01 00:00:00 | new | route6 | 2804:669c::/32AS269571 ⧉ | RADB | 1705491 |
| 2026-10-08 22:44:38 | new | as-set | AS269571:AS-TEX-TELECOM-ALL ⧉ | TC | 344389 |
| 2026-10-08 22:44:38 | new | as-set | AS269571:AS-TEX-TELECOM-CUSTOMERS ⧉ | TC | 344388 |
| 2026-10-08 22:44:38 | new | as-set | AS269571:AS-TEX-TELECOM ⧉ | TC | 344387 |
| 2026-10-08 22:44:38 | mod | aut-num | AS269571 ⧉ | TC | 344386 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:f000::/36AS269571 ⧉ | TC | 344385 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:e000::/36AS269571 ⧉ | TC | 344384 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:d000::/36AS269571 ⧉ | TC | 344383 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:c000::/36AS269571 ⧉ | TC | 344382 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:b000::/36AS269571 ⧉ | TC | 344381 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:a000::/36AS269571 ⧉ | TC | 344380 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:9000::/36AS269571 ⧉ | TC | 344379 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:8000::/36AS269571 ⧉ | TC | 344378 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:7000::/36AS269571 ⧉ | TC | 344377 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:6000::/36AS269571 ⧉ | TC | 344376 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:5000::/36AS269571 ⧉ | TC | 344375 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:4000::/36AS269571 ⧉ | TC | 344374 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:3000::/36AS269571 ⧉ | TC | 344373 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:2000::/36AS269571 ⧉ | TC | 344372 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:1000::/36AS269571 ⧉ | TC | 344371 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c::/36AS269571 ⧉ | TC | 344370 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:e000::/35AS269571 ⧉ | TC | 344369 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:c000::/35AS269571 ⧉ | TC | 344368 |
| 2026-10-08 22:44:38 | new | route6 | 2804:669c:a000::/35AS269571 ⧉ | TC | 344367 |