Google CloudSenior

Cloud Run 429 and 503: no instance available or instance limit reached

Cloud Run returns 429 or 503 when it hits max instances or a quota. Check the instance count metric, raise the limit or lower concurrency, and check timeouts.

What you see

  • HTTP 429 The request was aborted because there was no available instance.
  • HTTP 503 The Cloud Run service probably has reached its maximum container instance limit. Consider increasing this limit.
  • HTTP 503 The request failed because either the HTTP response was malformed or connection to the instance had an error.

What it means

429 and the first 503 are capacity signals. Traffic needs more instances than the service is allowed, or than the quota gives it. The second 503 is about the instance itself: a malformed response or a connection problem.

How to confirm the cause

  1. 1
    Check the container instance count metric
    # In Cloud Monitoring, open the Cloud Run "Container instance count" metric for the service.

    If usage is near the limit, capacity is the problem.

  2. 2
    Search logs for memory and liveness failures
    gcloud run services logs read SERVICE_NAME --region REGION

    Look for out-of-memory errors and liveness probe failures.

Causes and fixes

  • 429: no available instance

    HOW TO TELL
    Instance count is near the maximum.
    FIX
    Raise the maximum instances setting. If you need more capacity than your quota allows, request a quota increase.
  • 503: maximum instance limit reached under high concurrency

    HOW TO TELL
    Instance count is at the limit during a traffic peak.
    FIX
    Raise the maximum instances, or lower the per-instance concurrency.
  • 503: malformed response or connection error

    HOW TO TELL
    Logs show out-of-memory or liveness probe failures, or requests fail before the request timeout.
    FIX
    Fix memory use and increase the liveness probe timeout. Raise the framework timeout (Node.js server.setTimeout, Gunicorn's timeout). If a Serverless VPC Access connector is saturated, raise its max instances or instance type. Above 800 requests per second per instance, turn on HTTP/2.

How to stop it coming back

  • Load test to find the real instance count you need, then set max instances above it.
  • Alert when instance count reaches 80% of the maximum.

Keep going

Sources

Google Cloud documentation (docs.cloud.google.com), read 18 Nov 2026.

Search

Search cheat sheets and projects