Skip to main content
If you need help, have a technical inquiry, or want to request a model, reach out through the channels below.

Ask the Docs

Ask our AI assistant trained on AirCloud documentation.

Send Us a Message

Submit your inquiry through our Contact Us page.
For sales inquiries or technical support, feel free to reach out directly.

Hyunkyung Kim

For general inquiries, email
hk.kim@aieev.com.

Byungsoo Park

For technical inquiries, email
bspark@aieev.com.

​
What Can You Contact Us About?

  • How to use Air API
  • Air Container deployment issues
  • Model addition requests
  • Sales and technical consultation
  • Onboarding and organization setup
  • Other technical inquiries

​
Helpful Information to Include

Providing the following details helps us respond faster.
  • Organization or Project name
  • Feature in use (e.g., Air API, Air Container)
  • Description of the issue
  • Steps to reproduce
  • Screenshots or log output (if available)
  • For model requests: model name, intended use case, expected traffic or scale, and preferred response speed or deployment type

​
Common HTTP Errors

The following are frequently encountered issues and how to resolve them.
Authentication failed. Please verify your API key or access credentials.
The requested container ID or endpoint path is incorrect. Please check the container ID or route.
If an internal server error occurs, please try again later or contact the AirCloud support team at contact@aieev.com.

​
Troubleshooting

Common issues encountered during use and how to resolve them.
  • Symptom: API request authentication fails
  • Cause: Expired or invalid API key
  • Resolution:
    • Verify that the API key is still valid (check expiration)
    • Generate a new API key from the AirCloud dashboard
  • Symptom: GPU not detected when starting a container
  • Cause: Node instability or driver mismatch
  • Resolution:
    • Redeploy to a new instance
    • Check compatibility between the container runtime and GPU driver
  • Symptom: Container cannot connect to external endpoints
  • Cause: Incorrect port configuration, DNS issue, or firewall blocking
  • Resolution:
    • Verify that the container exposes the correct port and the service is listening
    • Test external connectivity using curl from inside the container
    • Check that outbound traffic is not blocked in security group settings
  • Symptom: Deployment stalls at the health check stage
  • Cause: The /health endpoint is not returning HTTP 200 OK
  • Resolution:
    • Confirm the correct health check URL and port are exposed
    • Review logs for error messages or model loading delays
  • Symptom: No scaling occurs despite high load
  • Cause: Scaling threshold set too high or replicas in an unhealthy state
  • Resolution:
    • Adjust autoscaling parameters such as CPU threshold and latency
    • Ensure all replicas pass health checks
  • Symptom: API returns a server error (502/503)
  • Cause: Application not bound to the expected port or crashed during startup
  • Resolution:
    • Confirm the service is running on 0.0.0.0:<PORT>
    • If model loading takes time, increase the health check timeout