no endpoints Kubernetes Origin: Platform & cloud Last updated 12 Oct 2026

Service has no endpoints (no endpoints available for service / Endpoints: <none>)

The Service’s selector matches no ready pods, so traffic to it is refused or returns 503.

Exact message you may see no endpoints available for serviceEndpoints: <none>service has no endpoints503 Service Temporarily Unavailable
Explore the map of this error Full error map →
Seen on: Kubernetes

Meaning

A Service forwards only to pods whose labels match its selector and which are Ready. A label typo, pods failing readiness, or a targetPort that doesn’t match the container port leave it empty or broken. Ingress controllers then return 503.

Common causes

  • Selector labels don’t match pod labels
  • Pods not Ready (readiness probe failing)
  • targetPort doesn’t match the containerPort/name
  • Service and pods in different namespaces

⚡ Quick fix

  1. Compare selector and pod labels
  2. kubectl get endpoints <svc> (or endpointslices)
  3. Fix readiness or targetPort

Detailed fix by platform

Kubernetes

  1. bash
    kubectl get svc web -o jsonpath='{.spec.selector}'; echo
kubectl get pods -l app=web --show-labels
kubectl get endpointslices -l kubernetes.io/service-name=web

How to diagnose

  1. Selector — Matches pod labels exactly?
  2. Ready — Pods READY 1/1?
  3. Ports — targetPort vs containerPort

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

0x80070422 — Windows Update error 0x80070422 (service is disabled) (Windows)0x80070422503 — HTTP 503 Service Unavailable (HTTP)503actively refused it — HttpRequestException: No connection could be made because the target machine actively refused it (localhost:5001) (.NET)actively refused itCannotPullContainerError — ECS task stopped: CannotPullContainerError: pull image manifest has been retried ... / ref pull has been retried (AWS)CannotPullContainerEr…default backend - 404 — Ingress returns "404 Not Found" / "default backend - 404" (ingress-nginx) (Kubernetes)default backend - 404DNS in pod — DNS not working inside a Kubernetes pod (could not resolve host / nslookup: can't resolve) (Kubernetes)DNS in podFailedCreatePodSandBox — Failed to create pod sandbox: plugin type="calico" failed (add): ... (FailedCreatePodSandBox) (Kubernetes)FailedCreatePodSandBoxNetworkOnMainThreadException — android.os.NetworkOnMainThreadException (Android)NetworkOnMainThreadEx…no endpoi…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.