Skip to main content

AS263641

ASN263641

TCF Telecomunicações Campo Florido Ltda

Registry

Authoritative registration data

AS number
263641
Name
ASN263641
Organisation
TCF Telecomunicações Campo Florido Ltda
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

20

IPv6 prefixes

8

Total announced

28

Announced prefixes

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

Prefixes announced by AS263641
179.127.152.0/21 IPv4 /21 not checked
168.205.60.0/22 IPv4 /22 not checked
168.205.60.0/23 IPv4 /23 not checked
168.205.62.0/23 IPv4 /23 not checked
179.127.152.0/23 IPv4 /23 not checked
179.127.154.0/23 IPv4 /23 not checked
179.127.156.0/23 IPv4 /23 not checked
179.127.158.0/23 IPv4 /23 not checked
168.205.60.0/24 IPv4 /24 not checked
168.205.61.0/24 IPv4 /24 not checked
168.205.62.0/24 IPv4 /24 not checked
168.205.63.0/24 IPv4 /24 not checked
179.127.152.0/24 IPv4 /24 not checked
179.127.153.0/24 IPv4 /24 not checked
179.127.154.0/24 IPv4 /24 not checked
179.127.155.0/24 IPv4 /24 not checked
179.127.156.0/24 IPv4 /24 not checked
179.127.157.0/24 IPv4 /24 not checked
179.127.158.0/24 IPv4 /24 not checked
179.127.159.0/24 IPv4 /24 not checked
2804:1094::/32 IPv6 /32 not checked
2804:7b40::/32 IPv6 /32 not checked
2804:1094:d000::/36 IPv6 /36 not checked
2804:1094:1000::/40 IPv6 /40 not checked
2804:1094:1100::/40 IPv6 /40 not checked
2804:1094:2000::/40 IPv6 /40 not checked
2804:1094:2100::/40 IPv6 /40 not checked
2804:1094:d000::/43 IPv6 /43 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 AS263641
Address families
DE-CIX New York: DE-CIX New York Peering LAN 10,000 Mbps IPv4 · IPv6
DE-CIX Sao Paulo 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 20,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 AS263641 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

18 networks seen before AS263641 in AS paths

Observed upstreams
Families
AS53427 817 4,935
v4 v6
AS268624 1,157 2,953
v4 v6
AS272713 52 971
v4
AS6939 HURRICANE 39 294
v4
AS137409 GSLNETWORKS-AS-AP 28 292
v4 v6
AS33891 CORE-BACKBONE 16 229
v4 v6
AS8966 Etisalat-AS 16 184
v4
AS34549 MEER-AS 19 180
v4 v6
AS6057 6057 14 113
v4 v6
AS8359 5 55
v4
AS61626 ASN61626 5 48
v4 v6
AS41327 FIBERTELECOM-AS 4 48
v4
AS64049 2 46
v4
AS32097 WII 2 24
v4
AS4230 ASN4230 3 23
v4
AS39120 2 23
v4
AS29632 NASSIST-AS 4 18
v6
AS17557 PKTELECOM-AS-PK 1 7
v4

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS263641 in AS paths

Observed downstreams
Families
AS271196 813 4,104
v4 v6
AS271420 456 1,390
v4 v6
AS274338 287 604
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

28 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 11 332
v4 v6
AS14840 ASN14840 5 168
v4 v6
AS199524 GCORE 11 98
v4 v6
AS51185 MAINSTREAMING-AS 6 82
v4 v6
AS28634 5 64
v4
AS271253 5 64
v4
AS60503 6 50
v4 v6
AS61573 6 50
v4 v6
AS263152 6 50
v4 v6
AS263237 6 50
v4 v6
AS22548 6 49
v4 v6
AS52873 ASN52873 5 49
v4 v6
AS36236 NETACTUATE 6 48
v4 v6
AS264479 6 48
v4 v6
AS22652 4 44
v4 v6
AS35280 F5 2 35
v4
AS37721 ORG-VTS1-AFRINIC 5 32
v4
AS262427 5 32
v4
AS835 GOCODEIT-EDGE 4 31
v4
AS209823 4 31
v4
AS45489 SLT-GLOBAL 4 30
v4
AS49544 i3Dnet 2 26
v4 v6
AS198150 SIACOM-AS 4 25
v4
AS1828 UNITAS 2 24
v4
AS28624 4 17
v6
AS271196 2 12
v4 v6
AS271420 1 8
v4 v6
AS274338 2 2
v4 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.