Status · live
All systems operational.
If you're seeing something broken, this page tells you whether we know about it. We update it before we update our Twitter, before we update our investors, before we update each other.
Operational · nothing on fire as of 19 May 2026, 9:46 am IST
Components
Recent incidents
14 May 2026 — Brief WhatsApp delivery delay (≈11 min)
Outbound WhatsApp messages were queued for an average of 11 minutes between 14:23 and 14:34 IST due to upstream rate-limiting from WhatsApp Business. All messages eventually delivered. No data loss.
02 May 2026 — OCR latency elevated (≈45 min)
OCR P95 latency rose from ~3s to ~12s between 10:11 and 10:56 IST. Cause: a misconfigured deployment of the vision pipeline that we caught on auto-rollback. No data loss; no failed drafts.
How we communicate during an incident
- This page updates first — the banner at the top changes within 5 minutes of detection.
- If you're a paying shop, you get a WhatsApp message inside 15 minutes of confirmation.
- Post-incident, we publish a written post-mortem within 14 days for anything that affected more than one shop. Linked here under the incident.
- We do not silently resolve. Every incident on this page closes with “Resolved” and a one-line root cause.
How to report something we're missing
The fastest way: WhatsApp the founder directly. The second fastest: email [email protected]. We'd rather chase one false report than miss a real one.
What this page doesn't do (yet)
We're a small team. We don't yet have a paged third-party status provider with green/yellow/red graphs. We will get one before the first incident this page reports involves more than two pharmacies. Targeted for Q3 2026.