CogniLead
ProductWarmed sender poolReputation circuit-breakerJurisdiction routingREST APIMCP serverDNS automationCompliance & suppression
SolutionsDevelopersAgenciesB2B SaaSRecruitersSales teamsSolo foundersSaaSRecruiting & staffingReal estateAgencies & consultingEcommerce & DTCB2B services
CompareAll 12 alternatives →vs. Instantly.aivs. Smartleadvs. Lemlistvs. Apollo.iovs. Woodpecker.coInstantly vs. SmartleadSmartlead vs. LemlistApollo vs. LemlistSee all 8 →
ResourcesBlogDocsMCP serverAPI referenceSPF checkerDMARC checkerBlacklist checkerSpam-word checkerStatus
PricingLog inStatus
CogniLead platform health.
Live readout for every component that powers the pipeline. Each row is a synchronous probe (1-second timeout) re-evaluated every 30 seconds.
Partially operational·3/5 healthy · 2 degraded
| Component | Status | Mode | Detail | Checked |
|---|---|---|---|---|
| Database | operational | pg | 2 tenants · 59ms | 13:43:25 |
| Stripe | configured | configured | live billing wired | 13:43:25 |
| Email (SES) | memory | memory | dry-run — no transport configured | 13:43:25 |
| Sender domain pool | memory | memory | no active sender_domains rows · using DEFAULT_POOL | 13:43:25 |
| MCP server | operational | npm | @cognilead/mcp-server@0.4.0 | 13:43:25 |
Legend
ok- Answering well under budget.
slow- Answered, but past the comfort threshold.
down- Probe failed.
configured- A managed third-party (Stripe, Amazon SES) is wired with a credential.
memory- Running on the local stub — fine for a demo, not production.
For monitors
The same data, same shape, as JSON — poll it from an uptime checker instead of scraping this page.
GET /status/jsonStatus pages NEVER expose environment values or secrets — only mode labels and elapsed-ms.