> For the complete documentation index, see [llms.txt](https://doc.sk5data.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sk5data.com/faq/proxy/what-is-the-difference-between-rotating-and-sticky-sessions.md).

# What Is the Difference Between Rotating and Sticky Sessions?

sk5data Residential Proxies support two session modes: **Rotating Sessions** and **Sticky Sessions**.

#### Rotating Sessions

A new residential IP address is automatically assigned for each request, making this mode ideal for tasks that do not require a consistent IP address.

Common use cases include large-scale web scraping, search result collection, and ad verification.

#### Sticky Sessions

Sticky sessions maintain the same residential IP address whenever possible for a specified duration.

SK5Data Residential Proxies support session durations of **1–120 minutes**.

This mode is suitable for tasks requiring continuous access, persistent login sessions, or multi-step operations.

**Note:** Sticky sessions do not guarantee that the IP address will remain unchanged under all circumstances. The exit IP may change if the session expires, the original IP becomes unavailable, or a network connection issue occurs.


---

# 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://doc.sk5data.com/faq/proxy/what-is-the-difference-between-rotating-and-sticky-sessions.md?ask=<question>&goal=<user_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.