# Support and status

API availability, collection freshness and editorial publication are independent signals.

## API availability
Check the actual request's HTTP status and body. A successful discovery response confirms that route answers; it does not prove every dataset is accessible or that your key is entitled. A successful empty query is not an outage.

## Collection freshness
Use source observation timestamps, [coverage](/coverage), and the [endpoint catalog](/data/endpoints.json). A functioning API can serve delayed collection. Compare the source-specific timestamps rather than treating page-load time as freshness.

## Editorial publication
The [Snapshot](/snapshot) and daily digest represent editorial output. A late editorial edition does not imply the underlying archive API is unavailable, and a new edition does not prove every collector succeeded.

## Get help
Email [contact@china-snapshot.com](mailto:contact@china-snapshot.com) with the endpoint, request time, status code and a redacted query. Never include a key. For key replacement, write from the address that received it.

## Coming soon
A dedicated consolidated public incident/status history is not implemented by this docs change. The signals above remain separate; this page does not invent a green operational badge.