Is EneUI down?
No guesswork: the same checks an engineer would run, re-run every 30 seconds, and published here with their timings. If this page loads, the server is answering, the question is what it can reach.
Live checks
| Check | Result | Time | Detail |
|---|---|---|---|
| Website | Operational | 0 ms | this response |
| Component catalog | Operational | 252 ms | 111,985 components indexed |
| Components API | Operational | 258 ms | 91 KB page built |
| Data storage | Operational | 1 ms | writable |
| Operational | 0 ms | outbox only (no provider key) |
Daily uptime
- 2026-11-02100.00%
- 2026-11-01100.00%
- 2026-10-31100.00%
- 2026-10-30100.00%
- 2026-10-29100.00%
Questions
Is EneUI down right now?
No. Every check on this page passed at 2026-11-02 22:09:30 UTC: the site, the component catalog, the components API and data storage are all responding.
How do I know the problem is EneUI and not my connection?
Open this page from another network, a phone on mobile data is enough. If this page loads and the checks are green, the problem is on your side: a proxy, an extension blocking scripts, or DNS. If this page also fails to load, the server itself is unreachable and the problem is ours.
Does EneUI have a status API I can monitor?
Yes. GET /health returns JSON with the same data as this page, status, per-check results, uptime, p95 latency, and needs no key. A monitor that expects HTTP 200 and status "operational" can watch it every minute.
What uptime does EneUI have?
The current process reports 100.00% over the last 1440 minutes, measured by an internal check every 30 seconds. Daily rollups go back 5 days, when the history is short, this page says so instead of quoting a number it cannot support.
Something is broken and this page says it is fine. What do I do?
Tell us the URL and what you see. A page that renders but a preview that stays blank is a component-level problem our uptime checks cannot detect: the catalog and the API can be healthy while one component's preview is not.
What you can call
GET /health, JSON: {"status","checks","uptimeSeconds","p95ms"}. No key, no cookies, safe for any monitor. It answers 503 when the status is down, so a plain HTTP check works too.