> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/announcement/zh-cn/nov-2025/20251118.md).

# 关于 Cloudflare 服务故障及已恢复的通知

尊敬的Cregis用户，

您好！今日 19:48（UTC+8）起，Cregis 部分服务受到 Cloudflare 全球性故障影响，可能导致部分用户在 API 调用及客户端访问时出现延迟或中断。经过紧急监控与处理，服务已于 22:34（UTC+8）恢复正常。

本次事件为 Cloudflare 全球性问题，不会对 Cregis 用户资产造成影响。\
如需了解更多信息，请访问 Cloudflare 官网公告。

我们将持续关注事件发展，如有任何问题，也会第一时间通知大家。

感谢您一直以来对 Cregis 的支持！如有任何疑问，请随时联系我们。

Cregis团队\
2025-11-18


---

# 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://support.cregis.com/announcement/zh-cn/nov-2025/20251118.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.