Try or ByeTry or Bye

Azure App Service HTTP 503 Service Unavailable / 502 Bad Gateway

Share
Workaround available Azure portal, Azure CLI, PowerShell Updated November 14, 2026How we research

Quick answer

503 and 502 on App Service usually mean slow requests, high CPU or memory, or an app exception. Check metrics, use Diagnose and solve problems, then scale or restart.

Most likely fix: Observe

How to fix it

Try these in order — the most common fix is first.

  1. 1. Observe

    1. Check service health notifications in the Azure portal
    2. Open your app > Monitoring > Metrics and watch CPU time, memory working set and requests
    Did this fix it?

  2. 2. Collect data

    1. Open Diagnose and solve problems on the app
    2. Open Development Tools > Advanced Tools > Go to use Kudu (log stream, diagnostic dump, debug console)
    Did this fix it?

  3. 3. Mitigate

    1. Scale up the App Service plan or scale out to more instances
    2. Configure auto-healing triggers to recycle the worker process
    3. Restart the app from the portal
    Did this fix it?

Symptoms

Your site on Azure App Service returns HTTP 502 Bad Gateway or HTTP 503 Service Unavailable.

Why it happens

  • Requests take a long time
  • App uses high memory or CPU
  • An exception prevents the app from responding
  • Azure service interruption

This guide also covers

  • azure app service 503
  • azure app service 502 bad gateway
  • azure web app service unavailable
  • azure app service http error 503

Still not working?

If Azure keeps failing, you're not alone. See every Azure problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

Other Azure errors