> For the complete documentation index, see [llms.txt](https://docs.ipwo.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipwo.net/kai-fa-zhe-wen-dang/chang-jian-cuo-wu/qing-qiu-pinlguo-gao.md).

# 请求频率过高

如果出现：

```
429 Too Many Requests
Rate Limit Exceeded
Too many requests
```

通常表示：

```
请求频率超过目标网站限制
```

这是数据采集、多账号运营、高并发请求中最常见的问题之一。

***

### 一、常见原因

#### 1. 请求过于频繁

短时间大量请求可能触发：

* 网站风控
* IP 限流
* 临时封禁

***

#### 2. 多账号共用一个 IP

多个账号同时使用同一 IP：

```
容易触发平台风控
```

***

#### 3. 并发过高

例如：

* 多线程
* 异步批量请求
* 爬虫高并发

***

#### 4. Session 使用不合理

频繁切换 IP 或 Session：

```
可能被识别为异常流量
```

***

### 二、常见报错示例

#### HTTP

```
429 Too Many Requests
```

***

#### Python

```python
requests.exceptions.HTTPError: 429
```

***

#### Node.js

```
Rate limit exceeded
```

***

### 三、推荐解决方案

#### ✔ 降低请求频率

建议：

* 增加请求间隔
* 随机 sleep
* 避免瞬间高并发

***

#### ✔ 使用粘性 Session

适用于：

* TikTok
* Facebook
* Amazon

示例：

```
username_custom_zone_us_session_abc123
```

***

#### ✔ 增加 Retry 重试机制

请求失败后：

```
延迟后重新请求
```

避免连续触发风控。

***

#### ✔ 分散 IP

推荐：

```
一个账号一个 IP
```

避免大量账号共用同一出口。

***

### 四、推荐排查流程

```
1. 检查请求频率
↓
2. 降低并发
↓
3. 增加 retry
↓
4. 使用粘性 Session
↓
5. 更换 IP 测试
```

***

### 五、开发建议

推荐：

* 控制并发数量
* 增加随机请求间隔
* 使用住宅代理
* 使用海外 VPS

避免：

* 高频无限循环请求
* 大量账号共享 IP
* 频繁切换国家地区

***

### 六、相关文章

* [API 调用与批量采集](/dai-li-ji-chu-zhi-shi/api-diao-yong-yu-pi-liang-cai-ji.md)
* [什么是粘性会话](/dai-li-ji-chu-zhi-shi/shen-me-shi-nian-xing-hui-hua.md)
* [什么是轮换 IP](/dai-li-ji-chu-zhi-shi/shen-me-shi-lun-huan-ip.md)
* [如何降低封禁风险](/dai-li-ji-chu-zhi-shi/ru-he-jiang-di-feng-jin-feng-xian.md)
* [Connection reset](/kai-fa-zhe-wen-dang/chang-jian-cuo-wu/connection-reset.md)
* [API 返回为空](/kai-fa-zhe-wen-dang/chang-jian-cuo-wu/api-fan-hui-wei-kong.md)


---

# 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://docs.ipwo.net/kai-fa-zhe-wen-dang/chang-jian-cuo-wu/qing-qiu-pinlguo-gao.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.