# Status and SLAs

> Track service health and understand the difference between an SLO and a contractual SLA.

Canonical: https://nolimitnodes.com/docs/status-and-slas

Check [status.nolimitnodes.com](https://status.nolimitnodes.com) for current service health, regional latency, and incident history.

## Service health

Monitor the endpoint used by your application:

| Product | Health signal |
|---|---|
| JSON-RPC | Authenticated `getHealth` |
| WebSocket | Successful upgrade and a small subscription |
| Yellowstone gRPC | `Ping` and `GetSlot` |
| Enhanced Streams | `ListTopics` |
| Program Streams | `ListTopics` |

## SLO and SLA

An SLO is a service target.

An SLA is a contract term with defined measurement rules and remedies.

Your order form and service agreement control your SLA.

Do not treat a marketing uptime value as a contractual promise.

## Incident response

During an incident:

1. Check the public status page.
2. Record endpoint, region, start time, and status code.
3. Reduce aggressive retries.
4. Switch to your tested fallback.
5. Keep request IDs and affected slots.
6. Contact support with the recorded details.

## Production health checks

- Run checks from each user region.
- Use authenticated requests.
- Track latency percentiles.
- Track error rate by protocol.
- Alert on sustained failures, not one request.
- Test fallback paths before launch.