> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/dataimpulse-documentation-es/proxies/tipos-de-conexiones.md).
# Tipos de conexiones
Ofrecemos dos tipos de conexiones de proxy: Rotating y Sticky.
### Rotativo
La dirección IP cambia automáticamente con cada nueva solicitud.
Deberías usar:
Para HTTP/HTTPS
823 PUERTO
Para SOCKS5
824 PUERTO
***
### **Sticky**
Los proxies sticky están basados en puertos. Las direcciones IP están vinculadas a un puerto específico por un período de tiempo.
El intervalo de rotación para los proxies sticky puede variar de 1 a 120 minutos, siendo la duración media de 30 minutos.
Para conexiones sticky, puedes usar puertos desde **10000** hasta **20000**.
Un ejemplo del proxy HTTP sticky:
```
curl -x "http://login:password@gw.dataimpulse.com:10000" https://api.ipify.org/
```
Un ejemplo del proxy SOCKS5 sticky:
```
curl -x "socks5://login:password@gw.dataimpulse.com:10000" https://api.ipify.org/
```
{% hint style="info" %}
Si no se especifica un Intervalo de Rotación para una conexión Sticky o se establece en "0", el intervalo por defecto será de 30 minutos.
{% endhint %}
***
Artículo del blog sobre cómo seleccionar el mejor tipo de proxy:
[Proxies Rotativos o Sticky: Cómo elegir la opción correcta](https://dataimpulse.com/blog/rotating-or-sticky-proxies-how-to-make-the-right-choice/)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dataimpulse.com/dataimpulse-documentation-es/proxies/tipos-de-conexiones.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
