System status

Live health of Ajeeb Personal. Updated on every page load. Last refresh: 2026-06-20 00:45 UTC.

Components

Incident history

2026-05-27 Major · ~2h

OpenAI SDK response.output None — WhatsApp chat unavailable for 2 hours

The OpenAI Python SDK returned response.output=null for a class of Codex calls. Our streaming path iterated the field directly, raised TypeError, and Hermes classified the error as non-retryable. Chat replies stopped for ~2 hours. Fix: patched both the SDK call site and the Hermes streaming handler to null-check before iteration.

2026-05-01 Critical · ~5d

Cross-account leak via Zernio webhook — all 4 instances paused for 5 days

Zernio (our IG/WA fan-in provider) routed messages from multiple connected Meta accounts to a single webhook URL without surfacing account_id at the handler. As a result, an Ajeeb instance auto-replied to DMs on accounts it should not have been touching (incl. 17 strangers via the 360 Camp IG during Eid Camp registration). We paused all four Ajeeb instances for 5 days while we rewrote the webhook handler to enforce account_id allowlists (default-deny) and added an outbound HARD_KILL gate. Postmortem: webhook handlers receiving multi-tenant fan-in must enforce explicit per-account ACLs.

2026-04-24 Critical · ~6d

WhatsApp Cloud API second-review ban — outbound suspended during probation

Meta placed our WhatsApp Cloud API number under second-review while it audited our messaging volume and template usage. Outbound was throttled; a number of automated nudges did not deliver. Probation closed cleanly on 2026-05-17 with no recurrence over the following 16 days. The permanent fix is the WhatsApp Business API migration on our roadmap.

Reporting

If you see something broken that is not on this page, write to support@ajeeb.ai or message Ajeeb on WhatsApp with /incident followed by what you saw. We respond within one business day and a major incident here within four hours.