Service unavailable, not responding or slow (503)

Symptom

The page shows one of these messages, or the API answers 503:

• «Could not reach AuthGuard. Make sure the service is running and try again.»
• «The service started, but the required components are not ready yet.»
• «The server took too long to respond. Try again.»
• «No network connection. Check your connection and try again.»
• At the top of the page: «Service · unavailable».

Cause

• Your network cannot reach the service (no internet, a proxy or a firewall).
• The service is restarting or a dependency (database, key management) is unavailable.
• The service is overloaded: 503 service_busy with Retry-After.

Fix

1. Check your internet connection and try another page.
2. Wait a minute and retry. In an integration, honour Retry-After.
3. If it fails only inside the company network, ask the network team to confirm the service address is not blocked.

When to escalate

If the problem lasts more than a few minutes or affects many people, contact support with the time, the exact message and the network you are on. During an outage, new sessions cannot be started through the service; sessions already open in applications continue until they expire.