> For the complete documentation index, see [llms.txt](https://docs.colt.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.colt.net/colt-docs/ja/status.md).

# ネットワーク状況とサービス可用性

当社ネットワークサービスの稼働状況に関する情報

Coltのステータスページへようこそ。ここでは、当社サービスの稼働状況に関する情報をご確認いただけます。

お近くのサポートをご希望の場合は、以下をクリックしてください：

<a href="https://colt.net/contact/support/" class="button primary">サポートチームにお問い合わせ</a>

### 現在の状況

{% hint style="success" %}
すべてのお客様向けプラットフォームは現在ご利用いただけます。
{% endhint %}

{% hint style="success" %}
すべてのシステムは正常に稼働しており、ご利用いただけます。
{% endhint %}

{% hint style="success" %}
ネットワークインフラは現在すべて正常に稼働しています。
{% endhint %}

### 最新情報

<details>

<summary>現在</summary>

お客様に影響するネットワークや接続の問題は確認されていません。問題が発生している場合は、サポートチームまでご連絡ください。

</details>


---

# 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://docs.colt.net/colt-docs/ja/status.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.
