IRRd3

Search

options
formatted raw json graphql resource page ⧉ 7.8 ms

AS52871

aut-numalso in: TC AS52871 hist
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 [dot] com [dot] br
                Peering issues / requests: peering [at] usetelecom [dot] com [dot] br
                Abuse and SPAM : abuse [at] usetelecom [dot] com [dot] 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 [dot] com [dot] br
mnt-by:         MAINT-AS52871
changed:        noc [at] usetelecom [dot] com [dot] br 20221229  #22:05:53Z
source:         RADB
last-modified:  2023-11-13T16:13:28Z
aut-numalso in: RADB AS52871 hist
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

Delegation as-blocks covering AS52871 — the delegating registry may differ from where the aut-num lives (transfers)

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:        ****************************
as-block AS1 - AS64511 hist
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 [at] canarie [dot] ca
mnt-by:         CANARIE-MNT
changed:        unread [at] ripe [dot] net 20000101
source:         CANARIE

Sets named AS52871:…

as-set:         AS52871:AS-CONE
descr:          ###########################################################################
                # Use Telecom / TASCOM own networks and the networks of its customer cone #
                ###########################################################################
members:        AS-TASCOM-CUSTOMERS
remarks:        ==========================================================
                Abuse/UCE: abuse [at] usetelecom [dot] com [dot] br
                Network: noc [at] usetelecom [dot] com [dot] br
                PeeringDB Page: http://as52871.peeringdb.com/
                Website: https://www.usetelecom.com.br
                ==========================================================
notify:         noc [at] usetelecom [dot] com [dot] br
mnt-by:         MAINT-AS52871
changed:        fbarbosa [at] usetelecom [dot] com [dot] br 20221206  #15:28:55Z
source:         RADB
last-modified:  2023-11-13T16:13:11Z

IPv4 routes (89)

IPv6 routes (3)

Member of sets

Plain search: AS2914 · 2001:db8::/32 · AS-SET-NAME · MAINT-AS2914 · free text — options above add source/class/inverse/match filters
IRRd-style: !iSET,1 !a4SET !a6SET !gAS<n> !6AS<n> !rP[,o|l|L|M] !mCLASS,PK !oMNT !sSRC !j-* !J-* !v · RIPE-style: -x -l -L -M PFX · -i ATTR VAL · -T CLASS · -t CLASS · -K · -s SRCS
APIs: POST /graphql {"query":"{ asn(asn:2914){ routes4Count memberOf } }"} · ?format=json on any search