Cloudflare Worker
Application routing, server rendering, API routes, and edge request handling.
Service status
Leavely status
Live readiness for the Leavely Cloudflare Worker, database connection, public health check, and monitoring coverage.
Operational
Current service state from a live database readiness check.
Uptime target
99.9%
Reliability target used for error-rate alerting.
Last checked
1 Sept 2026, 07:21
Displayed in UK time.
System components
This page does not expose customer data. It reports only public operational signals needed to understand service availability.
Database readiness
Database reachable in 410 ms.
Public health endpoint
/api/health is checked by an independent scheduled monitor and is available to customer monitors.
Monitoring pipeline
Worker observability, assigned uptime incidents, and source-managed edge alert policy are configured.
Monitoring coverage
Independent checks and edge alerts
Monitoring combines Worker observability, an external scheduled readiness check, assigned GitHub incidents, and a source-managed Cloudflare error-rate policy.
Cloudflare Workers observability
Worker logs are persisted through Wrangler observability so errors and request traces can be reviewed after an incident.
Independent uptime alerting
A source-managed GitHub check calls the readiness endpoint twice an hour and opens an incident assigned to the service owner after repeated failure.
Edge error-rate policy
A weekly source-managed Cloudflare policy sync keeps elevated 5xx notifications reconciled with the 99.9% reliability target.
Readiness endpoint
The public health check verifies the Worker can serve requests and complete a database round trip.
Use /api/health for uptime monitors and /status for the human-readable status page.