Last check 22:53 UTC · . Checked every minute: this page is current until 22:56 UTC. If that time has passed, the checker has stopped and this page is out of date.
Website
hoursready.com: calculators, Rules Library
✓ Operational
Response time 19 ms (24 h median 16 ms). Checked 22:53 UTC.
90 days ago99.49% up since Nov 10, 2026 (8 min with no check, not counted as up)Today
UpPartly downDownNo data
Account app
app.hoursready.com: sign-in and accounts
✓ Operational
Response time 113 ms (24 h median 127 ms). Checked 22:53 UTC.
90 days ago99.49% up since Nov 10, 2026 (8 min with no check, not counted as up)Today
Upload tools
app.hoursready.com/upload
– Not yet launched
Not checked until the upload tools go live.
Incident notes
: Website and account app unreachable through Cloudflare (error 526). Resolved.
Visitors to hoursready.com and app.hoursready.com got a Cloudflare "526 Invalid SSL certificate" error page instead of HoursReady. The server itself was running and answering normally the whole time. The problem was in the secure connection between Cloudflare and our server: Cloudflare's encryption setting no longer accepted the certificate our server presents.
Started: Nov 11, 2026 at about 06:12 UTC. The exact start is not known; the error was first reported at 06:15 UTC.
Resolved: before 06:20 UTC. Our server's logs show pages being served through Cloudflare again from 06:20 UTC.
Duration: about 8 minutes.
Impact: website and account app pages could not be opened through the public address. No data was lost or exposed.
This page said "Operational" during the outage. At that time the checker only tested the server directly, not the public address, so it could not see the problem. The minute history above still records those minutes as up; we have not edited it, so the uptime figures for Nov 11 are too high by about 8 minutes. Since Nov 11, 2026 the checker also tests every part through the public address, the way visitors reach it, and shows a part as down if either check fails.
How this page works
A checker on the HoursReady server opens each part every minute, twice: once directly on the server and once through the public address (through Cloudflare), the way visitors reach it. A part counts as down when either check fails, and the page says which one. It logs only whether each check answered and how fast.
Uptime counts only the time since monitoring started (Nov 10, 2026). Minutes with no check are shown as no data, never as up.
This page is hosted on the same server as HoursReady, so if the whole server is down, this page is down too. An independent outside monitor is planned with the Enterprise plan's uptime commitment.