Support
Answers fast. Humans when it matters.
Search guides and docs, check platform status, or reach our team, most questions are solved in self-service without opening a ticket.
/health returns 503 during rollout. Try increasing healthCheckTimeout to 30s in service settings.Replied in 12 min · avg Pro response <4h
Response times
Support by plan
| Plan | Channel | Typical response |
|---|---|---|
| Hobby | Community forum | Best effort |
| Starter | 1 business day | |
| Propopular | Email + live chat | < 4 hours |
| Enterprise | Slack + named SE | < 1h P1 |
Self-service
Debug before you open a ticket
Most deployment issues are visible in build logs or health checks. Run these from your terminal with the StackBlaze CLI installed.
CLI referencestackblaze logs --service api --buildSee why the last deploy failed
curl https://your-app.stackblaze.app/healthVerify your health endpoint returns 200
stackblaze env list --service apiConfirm secrets are set in the right environment
FAQ
Common questions
Check the build logs for the failing step. Common causes: missing environment variables, wrong Node.js version, or a failed health check endpoint. Troubleshooting guide →
Contact
Still need help?
Pick the channel that matches your plan. Include service name, region, and relevant log lines for the fastest resolution.
Live chat
Chat with support directly in the dashboard. Available for Pro and Enterprise plans during business hours.
Email support
Send us a message with logs, service name, and timestamps. We respond faster when context is included.
Community
Ask the community, share blueprints, and learn from migration stories. Staff-replied threads weekly.
Documentation
Reference docs, API specs, CLI commands, and step-by-step guides for every feature.