Status
TCP v2 is four public hosts. This page lists what they are, where they are, and how to check them yourself.
This page is static, and that is deliberate
The public entry site makes no network requests — it does not query the API and it does not poll a health endpoint. Its content security policy sets connect-src to none, which means the browser itself blocks any request originating from this page. So this page cannot show you live status; it can only tell you where to look.
We think that is the right trade. A public, unauthenticated page that automatically polls a backend is also an amplification tool. And a claim of «zero authenticated calls» that the browser enforces is worth considerably more than the same claim written in a document.
Hosts
- v2.tcp.enlightenmentlab.dev
- The public entry site — this page · Authentication: none
- app-v2.tcp.enlightenmentlab.dev
- Analyst workbench · Authentication: TCP-ANALYSTS realm
- admin-v2.tcp.enlightenmentlab.dev
- Admin console · Authentication: TCP-ADMIN realm
- api-v2.tcp.enlightenmentlab.dev
- Control-plane API · Authentication: bearer token
Check it yourself
The API health endpoints require no authentication. Both of these open in a browser or in curl:
- https://api-v2.tcp.enlightenmentlab.dev/healthz
- Liveness. A 200 means the process is up.
- https://api-v2.tcp.enlightenmentlab.dev/readyz
- Readiness. Reports its connectivity to Postgres, ClickHouse, Redis and object storage.
Current environment
- Environment
- review
The values above come from a runtime configuration file written when the container starts, not compiled into the bundle. One image serves both the review and the canonical hostnames without a rebuild.
Incident reporting
There is no public incident timeline yet. If you hit an outage, please tell us using the address on the contact page.