> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/products/cn/dai-li/dedicated-datacenter-proxies/self-service/fair-usage-policy.md).

# 公平使用政策

为确保服务稳定并防止任何潜在的流量滥用，Oxylabs 会限制所提供的独享数据中心代理的并发会话数。可用的并发会话数取决于计费周期内每 1 个独享数据中心代理所使用的流量总量：

* **当每 1 个独享数据中心代理在一个月内的使用量未达到 100 GB 时，** 每购买 1 个独享数据中心代理最多可用 100 个并发会话（例如，购买 100 个独享数据中心代理意味着，在使用量达到 10,000 GB 之前，将可用 10,000 个并发会话）；
* **如果每 1 个独享数据中心代理的使用量达到 100 GB，** 在当前计费周期剩余时间内，每 1 个独享数据中心代理可用的并发会话数将降至 10 个（例如，购买 100 个独享数据中心代理并达到 10,000 GB 的使用量，意味着在当前计费周期结束前将可用 1,000 个并发会话）。

代理使用量会被自动跟踪，并在达到数据额度的 80% 和 100% 时发送电子邮件通知。一旦达到公平使用限制的 100%，并发会话限制将自动生效。

如果您需要任何帮助，请随时通过以下方式联系我们： [**support@oxylabs.io**](mailto:support@oxylabs.io) 或通过我们网站上的 24/7 在线聊天 [**网站**](https://oxylabs.io/).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.oxylabs.io/products/cn/dai-li/dedicated-datacenter-proxies/self-service/fair-usage-policy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.