What this status page covers
This page reports the live health of the parts of DoseRoutine that people depend on day to day: the sign-in service, the dose scheduler and reminder queue, the compound library and interaction checker, the photo-based meal scanner, and the sync layer that copies your logs between your phone and the web app. Each check runs against the same production systems you use, so a green marker here means a real request succeeded, not that a server was merely reachable.
Checks refresh whenever this page loads. If a component is degraded we describe what still works — for example, reminders can continue firing on your device while the sync layer catches up, because scheduled notifications are stored locally as well as on the server.
How we handle incidents
When something breaks we prioritize anything that can cause a missed or duplicated dose, because that is the failure that actually matters in a medication tracker. Reminder delivery and dose logging come first, then interaction data, then secondary features such as analytics, exports and the meal scanner.
Your logged doses are never dropped during an outage. The app writes them locally first and replays them to the server once connectivity returns, so a network failure delays sync rather than losing history. If you open the app offline you will still see today's schedule, your active protocols and your recent logs.
If the app is not working for you
If every component here reads healthy but the app still misbehaves, the cause is usually local: a stale cached build, a browser extension blocking scripts, or notification permissions that were revoked at the operating-system level. Pulling to refresh, reinstalling the home-screen app, or re-enabling notification permission resolves most of these.
Persistent problems are worth reporting. Tell us the page you were on, what you expected, and roughly when it happened, and we can match it against server logs for that window.