Error AtlasError Documentation and Resolution
Back to search

Cloud Run

Cloud Run returns HTTP 500 because no instance was available

HTTP 500 The request was aborted because there was no available instance.

Cloud Run returned an internal server error because the platform could not keep up with the incoming rate of traffic or request processing demand.

HTTP 500 The request was aborted because there was no available instanceruntime

Observed message

HTTP 500 The request was aborted because there was no available instance.

Why it happens

  • The service experienced a sudden traffic increase and could not scale quickly enough.
  • Request processing time is too long, which reduces the pool of available instances.
  • Cold starts or max-instances constraints contributed to an instance shortage.

How to fix it

  1. Inspect Cloud Monitoring and Cloud Logging around the failure window for traffic spikes, cold starts, and capacity limits.
  2. Implement retries with exponential backoff for clients that can safely retry transient failures.
  3. Improve startup and request handling performance, and review whether the current max-instances setting is too restrictive.

Official reference

Google Cloud: Troubleshoot Cloud Run issues

Related errors

While handling this request, the container instance was found to be using too much memory and was terminated.Cloud Run container instance was using too much memory and was terminatedHTTP 500 error codes in the logsCloud Run deployment succeeded but logs show HTTP 500 errorsHTTP 429 The request was aborted because there was no available instanceCloud Run request aborted because there was no available instanceHTTP 503 The request failed because either the HTTP response was malformed or connection to the instance had an errorCloud Run request failed because the response was malformed or the instance connection failed

Explore more

runtimeBrowse more runtime errors
Cloud Run HTTP 500 no available instance: causes and fixes | Error Atlas