> For the complete documentation index, see [llms.txt](https://www.axisnow.io/zh/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.axisnow.io/zh/docs/edge/endpoints/origin-address/faq.md).
# 常见问题
源地址健康检查的常见疑问与排错
源站明明挂了，为什么没有剔除？
按顺序排查：源地址只有一个地址（域名只解析出一个 IP），不会剔除；失败类型是否计入，源站返回 500 Internal Server Error、503 Service Unavailable 或 4xx 不计入，只有连接失败、超时和 502 Bad Gateway、504 Gateway Timeout 计入；是否达到阈值，默认要在 120 秒内失败 10 次，低流量的源地址可能攒不够；判断按边缘独立进行，只有经过该边缘的失败才在该边缘计数。
事件显示已剔除，为什么流量还打到那个地址？
剔除只在产生事件的那个边缘生效，其他边缘仍按自己的判断分配。剔除时长到期后流量自动恢复，真实流量监测下源站未恢复会再次剔除，中间有一批请求打过去。一个源地址的全部地址都被剔除时，请求回退到第一个地址继续回源。
事件里只有剔除没有恢复？
真实流量监测没有恢复判定，剔除到期即恢复，不记事件；恢复事件只由主动 TCP 探测产生。要看到恢复事件、并让地址在源站恢复前保持剔除，开启主动探测。
剔除时长到了源站还没恢复会怎样？
没有开启探测时地址回到轮询，失败再次累计到阈值后再次剔除；开启探测时地址保持剔除，直到探测连续成功 3 次，见[剔除与恢复](/zh/docs/edge/endpoints/origin-address/health-check.md#ejection)。
主动探测会给源站带来多少压力？
每个有流量经过的边缘对源地址的每个地址每 10 秒建立一次 TCP 连接，不发送请求内容。对某个地址的最后一次回源后约 30 分钟探测停止，没有流量的源地址不会被探测。
域名型地址的解析结果变了，健康状态怎么处理？
每个边缘按 DNS 记录的 TTL 重新解析，最短 30 秒、最长 120 秒。新出现的 IP 默认健康，立即参与分配；退出解析的 IP 不再分配，它的剔除状态随剔除时长过期。地址以 IP 为单位判断，域名解析出的多个 IP 各自剔除和恢复。
错误率不为 0，但没有发生剔除？
错误率是观测口径，剔除只看连接失败、超时和 502、504，见[洞察与日志](/zh/docs/edge/endpoints/origin-address/insight.md#insight)。
---
# 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://www.axisnow.io/zh/docs/edge/endpoints/origin-address/faq.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.