# Get help

Source: https://docs.quake.ai/docs/get-help
Markdown: https://docs.quake.ai/docs/get-help.md
> Where to start when something on Quake AI fails: status, troubleshooting, support tickets, and what evidence to bring.

---

# Get help

Most issues on Quake AI have a fast self-service path. This page is the canonical entry point: it tells you which path to take based on the symptom, and what to bring when you escalate to support.

## Decision tree

| What's happening                                          | Start here                                                                                         |
| --------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Service-wide outage suspected                             | [status.rumble.cloud](https://status.rumble.cloud) for the live status of platform services.       |
| Specific symptom you have seen before                     | [Operational runbooks](/docs/operate/runbooks): instance connectivity, volume issues, K8s.        |
| Diagnosing a quota error or limit                         | [Quota and limits troubleshooting](/docs/operate/troubleshooting/quota-and-limits).                |
| Auth, token, or credential failure                        | [Authentication and token diagnostics](/docs/operate/troubleshooting/auth-token-diagnostics).      |
| Pricing or invoice question                               | [How billing works](/docs/account/billing/how-billing-works) and [pricing reference](/docs/account/billing/pricing). |
| API error code you do not recognize                       | The per-service API error references: [Compute](/reference/compute/api-errors), [Network](/reference/network/api-errors), [Block Storage](/reference/block-storage/api-errors), [Object Storage](/reference/object-storage/api-errors), [Automation](/reference/automation/api-errors). |
| Need to escalate (none of the above resolved it)          | [Open a support ticket](https://rumble.cloud/support).                                             |

## Before you open a support ticket

Support resolves a clean ticket faster than a vague one. The [support ticket evidence collection](/docs/operate/troubleshooting/support-ticket-evidence) checklist is the canonical list of what to attach. The short version:

1. Project ID and region (the `us-east-1` / `us-east-2` / `us-west-1` you were working in).
2. Resource identifiers: instance, volume, network, bucket UUIDs.
3. The exact command or API call that failed and its full output (including request IDs).
4. The time window of the incident in UTC.
5. Anything you have already tried.

If the issue is intermittent, run the failing command with `--debug` (OpenStack CLI) or with verbose logging on your tool of choice and attach the captured output.

## Channels and what they are for

- **[status.rumble.cloud](https://status.rumble.cloud)**: current service status and incident history. Check this first; it answers "is the issue on my end?" in seconds.
- **[Open a support ticket](https://rumble.cloud/support)**: the primary escalation channel for technical, billing, and account issues. Support processes SLA credit claims only through tickets.
- **[Documentation](/docs)**: runbooks, troubleshooting guides, and reference docs. Report documentation errors through a support ticket.

## Related references

- [Operational runbooks](/docs/operate/runbooks): step-by-step recovery for known incident shapes.
- [Troubleshooting](/docs/operate/troubleshooting): diagnostic guides for common platform symptoms.
- [Service Level Agreement](/docs/account/sla): availability targets and credit eligibility.
- [Support ticket evidence collection](/docs/operate/troubleshooting/support-ticket-evidence): the full checklist before you escalate.