Skip to main content

AS271042

ASN271042

BOT INTERNET E SERVICOS DE TELECOMUNICACOES LTDA

Registry

Authoritative registration data

AS number
271042
Name
ASN271042
Organisation
BOT INTERNET E SERVICOS DE TELECOMUNICACOES LTDA
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

19

Total announced

26

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS271042
177.36.16.0/22 IPv4 /22 not checked
177.36.16.0/23 IPv4 /23 not checked
177.36.18.0/23 IPv4 /23 not checked
177.36.16.0/24 IPv4 /24 not checked
177.36.17.0/24 IPv4 /24 not checked
177.36.18.0/24 IPv4 /24 not checked
177.36.19.0/24 IPv4 /24 not checked
2804:7560::/32 IPv6 /32 not checked
2804:7560::/33 IPv6 /33 not checked
2804:7560:2000::/35 IPv6 /35 not checked
2804:7560:4000::/35 IPv6 /35 not checked
2804:7560:6000::/35 IPv6 /35 not checked
2804:7560:8000::/35 IPv6 /35 not checked
2804:7560::/35 IPv6 /35 not checked
2804:7560:a000::/35 IPv6 /35 not checked
2804:7560:c000::/35 IPv6 /35 not checked
2804:7560:e000::/35 IPv6 /35 not checked
2804:7560:2000::/40 IPv6 /40 not checked
2804:7560:2100::/40 IPv6 /40 not checked
2804:7560:1::/48 IPv6 /48 not checked
2804:7560:3::/48 IPv6 /48 not checked
2804:7560:4::/48 IPv6 /48 not checked
2804:7560:5::/48 IPv6 /48 not checked
2804:7560:6::/48 IPv6 /48 not checked
2804:7560:7::/48 IPv6 /48 not checked
2804:7560:8::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS271042
Address families
IX.br (PTT.br) Belo Horizonte: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Rio de Janeiro: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS271042 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS271042 in AS paths

Observed upstreams
Families
AS52468 2,889 13,625
v4 v6
AS37468 ORG-AC4-AFRINIC 1,583 2,802
v4 v6
AS264963 131 559
v6
AS137409 GSLNETWORKS-AS-AP 36 209
v4 v6
AS6057 6057 28 126
v4 v6
AS53427 42 42
v4
AS7713 telkomnet-as-ap 8 12
v4
AS61626 ASN61626 3 8
v4
AS39120 3 7
v4 v6
AS53013 ASN53013 1 3
v6
AS272713 1 2
v6

No rows match “”.

Showing of

Observed downstreams

11 networks seen after AS271042 in AS paths

Observed downstreams
Families
AS264598 1,249 2,567
v4 v6
AS273585 334 2,490
v4 v6
AS267978 ASN267978 457 1,516
v4 v6
AS270951 ASN270951 620 1,143
v4 v6
AS273348 262 1,038
v6
AS263508 272 1,006
v6
AS266010 ASN266010 459 678
v4 v6
AS264948 275 344
v4
AS270641 245 318
v6
AS264886 9 9
v4
AS268106 2 4
v6

No rows match “”.

Showing of

Uncertain adjacencies

28 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS14840 ASN14840 5 144
v4 v6
AS24482 SGGS-AS-AP 10 90
v4 v6
AS51185 MAINSTREAMING-AS 10 53
v4 v6
AS22548 10 46
v4 v6
AS60503 10 46
v4 v6
AS199524 GCORE 10 46
v4 v6
AS263237 10 46
v4 v6
AS36236 NETACTUATE 10 45
v4 v6
AS263152 10 45
v4 v6
AS52873 ASN52873 8 42
v4 v6
AS28624 9 39
v6
AS264479 9 38
v4 v6
AS28634 3 16
v4
AS271253 3 16
v4
AS262427 3 8
v4
AS273585 1 7
v6
AS52320 52320 3 6
v6
AS37721 ORG-VTS1-AFRINIC 2 6
v4
AS270951 ASN270951 1 4
v4 v6
AS263508 1 3
v6
AS273348 1 3
v6
AS264598 1 2
v6
AS267978 ASN267978 1 2
v6
AS29049 1 1
v4
AS198150 SIACOM-AS 1 1
v4
AS264948 1 1
v4
AS266010 ASN266010 1 1
v6
AS270641 1 1
v6

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.