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

# The status page

The Ticket King team maintains a public status page.

## Where to find it

[**status.ticketking.xyz**](https://status.ticketking.xyz)

{% embed url="<https://status.ticketking.xyz>" %}

The status indicator in the dashboard also links here.

## What it shows

* **Bot.** Whether the Discord bot is connected and responding.
* **API.** Whether the service the dashboard and bot rely on is responding.
* **Dashboard.** Whether the website is up.
* **Transcripts.** Whether the transcript viewer works.

## When to check it

* You see "This interaction failed" on a panel button. Check whether the bot is down.
* The dashboard will not load. Check whether the dashboard is down.

## Incidents

When something is wrong, the status page shows the affected part, when the incident started, and updates until it is resolved. You can subscribe on the page to get alerts.

## Maintenance

Planned maintenance is announced ahead of time in `#announcements` in the support Discord and on the status page.

## If an incident is already shown

If the status page already shows an active incident, you do not need to report it. Watch the page for updates.

## Related

{% content-ref url="/pages/dZKa2XV9PIaCVaCgC18j" %}
[Joining the support Discord](/docs/get-help-and-community/joining-support-discord.md)
{% endcontent-ref %}

{% content-ref url="/pages/X2RSLKZ1mcJ29yoOhGFn" %}
[Reporting bugs](/docs/get-help-and-community/reporting-bugs.md)
{% endcontent-ref %}


---

# 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://ticketking.xyz/docs/get-help-and-community/status-page.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.