> 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/common-questions/will-port-configurations-be-retained-after-an-unlimited-residential-proxy-ports-plan-expires.md).

# Will Port Configurations Be Retained After an Unlimited Residential Proxy (Ports) Plan Expires?

No.

Once your SK5Data Unlimited Residential Proxies (Ports) plan expires, the associated ports will stop working, and their configurations will no longer be retained.

#### What Happens After Expiration?

* **Ports become inactive** and stop providing proxy services.
* Expired ports can no longer be used or edited.
* Existing configurations, including location, rotation settings, authentication details, and remarks, will not be retained.
* Expired port plans cannot be renewed.

#### How to Avoid Service Interruptions

1. Go to the **Unlimited Residential Proxies (Ports)** usage page.
2. Check the expiration date of your purchased plan.
3. Renew your plan before it expires.
4. Save any configuration details needed for your tasks in advance.

**Note:** Once your plan expires, the ports will be disabled and their configurations will not be retained. Please renew before expiration.


---

# 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/common-questions/will-port-configurations-be-retained-after-an-unlimited-residential-proxy-ports-plan-expires.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.