Get help
Explanation · Updated Jun 2026
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 for the live status of platform services. |
| Specific symptom you have seen before | Operational runbooks: instance connectivity, volume issues, K8s. |
| Diagnosing a quota error or limit | Quota and limits troubleshooting. |
| Auth, token, or credential failure | Authentication and token diagnostics. |
| Pricing or invoice question | How billing works and pricing reference. |
| API error code you do not recognize | The per-service API error references: Compute, Network, Block Storage, Object Storage, Automation. |
| Need to escalate (none of the above resolved it) | Open a support ticket. |
Before you open a support ticket#
Support resolves a clean ticket faster than a vague one. The support ticket evidence collection checklist is the canonical list of what to attach. The short version:
- Project ID and region (the
us-east-1/us-east-2/us-west-1you were working in). - Resource identifiers: instance, volume, network, bucket UUIDs.
- The exact command or API call that failed and its full output (including request IDs).
- The time window of the incident in UTC.
- 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: current service status and incident history. Check this first; it answers "is the issue on my end?" in seconds.
- Open a support ticket: the primary escalation channel for technical, billing, and account issues. Support processes SLA credit claims only through tickets.
- Documentation: runbooks, troubleshooting guides, and reference docs. Report documentation errors through a support ticket.
Related references#
- Operational runbooks: step-by-step recovery for known incident shapes.
- Troubleshooting: diagnostic guides for common platform symptoms.
- Service Level Agreement: availability targets and credit eligibility.
- Support ticket evidence collection: the full checklist before you escalate.
See Also
Was this page helpful?