Health check¶
Your CDN node exposes a simple, public health endpoint so you can confirm at a glance that the node is up and serving — without needing your S3 credentials.
How to check¶
Send an HTTP request to port 8888 on your node's hostname:
http://your-node.clearstreamer.com:8888/healthz
Use the hostname from your welcome email in place of your-node.clearstreamer.com.
Any path on port 8888 works, but /healthz is the canonical one.
curl http://your-node.clearstreamer.com:8888/healthz
Open http://your-node.clearstreamer.com:8888/healthz in any browser.
A healthy node responds with HTTP 200 and:
{"status":"ok"}
This endpoint is plain HTTP on port 8888
The health check runs over plain HTTP on port 8888 — not HTTPS on 443. It carries no sensitive data, so there's no TLS and no certificate involved. Your actual S3 traffic still goes over HTTPS on port 443 as normal. If your network blocks outbound connections to port 8888, the check will time out even when the node is fine.
What it does — and doesn't — tell you¶
The health check is a liveness probe. A 200 {"status":"ok"} means the node is
running and accepting connections.
It intentionally does not check your credentials, your whitelist IP, or anything account-specific — so a successful health check does not by itself mean your requests will succeed.
Using it to narrow down a problem¶
If you can't connect to your S3 endpoint, the health check tells you where to look:
:8888/healthz result |
What it means | Where to look |
|---|---|---|
200 {"status":"ok"} |
The node is up and serving | The issue is on the request side — check your whitelist IP, credentials, and addressing |
| Times out / refused | The node isn't reachable from your network, or is down | Confirm outbound port 8888 isn't blocked locally; if it still fails, open a support ticket |
In other words: node up but S3 failing → it's almost always your credentials or whitelist IP, not the node. See Connection errors.