Skip to content
Live status

System Status

Real-time probes to 5 endpoints — measured from the edge, no mock data.

Updated —Local file (dev)
Checking…
Major outage — most probes failed.
Probes run in parallel · timeout 5s · no-storeAPI Docs →
Services — live latency & uptime4 probed
Service
7d90d
API Endpoints
0ms · api
—
7d
—
90d
SVG Generation
0ms · svg
—
7d
—
90d
PNG / WebP
0ms · png
—
7d
—
90d
Search Engine
0ms · search
—
7d
—
90d
Uptime — 7 days
—
Collecting history…

No probes recorded yet. Every refresh and every scheduled check is stored — this timeline fills with real data from now on. Nothing is fabricated.

Recorded probes — local file (set DATABASE_URL to persist)Auto-refresh 30s
Incidentsnone recorded
No data yet — incidents will appear here if any probe ever fails.
How this is real

Each refresh hits /api/status which fetches 5 real endpoints in parallel (SVG, PNG, search, categories, list) with no-store and 5s timeout. Latency and ok/fail are measured live — not mocked — and every run is appended to our database, so the 7D / 90D / 12M charts show only probes that actually happened.

GET /api/status
→ { status, avgResponseTime, services: [{id, ms, ok}], checks }
Where history lives

Every probe run is written to our own Postgres database (schema hylab_status) — per-day, per-service buckets, a run log and an incident log. It survives restarts, redeploys and machine changes, so the history accumulates for months and years. A daily Vercel Cron (/api/cron/probe) records even with no visitors; opening this page probes every 30s on top.

5 probesparallelPostgresdaily cron
Explore icons
26,150 ready to use
Browse →