Skip to content
Documentation

Get help

Explanation · Updated Oct 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 happeningStart here
Specific symptom you have seen beforeOperational runbooks: instance connectivity, volume issues, K8s.
Diagnosing a quota error or limitQuota and limits troubleshooting.
Auth, token, or credential failureAuthentication and token diagnostics.
Pricing or invoice questionHow billing works and pricing reference.
API error code you do not recognizeThe 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. If you do not have a portal account yet, email [email protected].

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:

  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#

  • Help desk: the escalation channel for technical, billing, and account issues. Support processes SLA credit claims only through tickets. If you do not have a portal account yet, email [email protected].
  • Documentation: runbooks, troubleshooting guides, and reference docs. Report documentation errors through a support ticket.
Was this page helpful?