Dedicated Endpoints expose two separate status types:Documentation Index
Fetch the complete documentation index at: https://docs.tokenfactory.nebius.com/llms.txt
Use this file to discover all available pages before exploring further.
- Lifecycle - What stage the deployment is in
- Readiness - Whether the endpoint can currently serve traffic
Lifecycle Status
Starting
Endpoint is being created or started.Provisioning is in progress, and traffic may not be available yet.
Updating
Endpoint is applying configuration changes.Traffic may continue, but capacity can temporarily degrade.
Running
Endpoint is deployed and expected to operate normally.Error
A deployment issue requires attention.The endpoint may still serve traffic depending on readiness.
If unresolved for more than 3 hours, contact support.
Stopping
Stop was requested, but shutdown is still in progress.Stopped
Endpoint is intentionally disabled.Readiness Status
Not ready
Endpoint cannot reliably serve requests. Expected during: Starting, Stopping, or StoppedPartially ready
Endpoint can serve traffic, but below expected capacity.Some replicas are still starting, updating, or unavailable.
If unresolved for more than 3 hours, contact support.
Ready
Endpoint is fully provisioned and ready for expected traffic.Common Status Examples
| Lifecycle | Readiness | Meaning |
|---|---|---|
| Starting | Not ready | Provisioning |
| Starting | Partially ready | Serving, still scaling |
| Updating | Ready | Serving normally during update |
| Running | Ready | Fully operational |
| Running | Partially ready | Degraded capacity |
| Running | Not ready | Unexpected outage |
| Error | Ready | Serving, but deployment issue exists |
| Error | Not ready | Deployment failure |
| Stopping | Partially ready | Shutting down |
| Stopped | Not ready | Fully stopped |
Key PrincipleLifecycle is deployment state. Readiness is traffic-serving capability.Use Readiness to decide whether to send traffic.