Skip to content
SERVICE STATUS

A clear view
when it matters.

The current health of Leadvera, checked live when you open this page.

Checking now
Get help

Checking the service…

The workspace, its database and file storage answer a live health check each time this page loads.

Workspace and APISign-in, the CRM workspace and its APIChecking…
DatabaseCloudflare D1: leads, contacts and every other recordChecking…
File storageCloudflare R2: documents and attachmentsChecking…
Database migrationsEvery schema update appliedChecking…
Lead intakeCalls, email, social and website lead sourcesChecking…
Email and messaging deliverySent through each workspace’s connected providerDepends on your workspace
Optional AIOff unless a workspace enables itDepends on your workspace

Incident history

No incidents recorded since launch.

Keep people informed.

Every update explains the affected functions, the next steps and the latest confirmed information.

Use the correct notice route.

A public status update does not replace a required security or personal-data incident notice.

Keep the next step available.

AI failures fall back to people, and each channel retries and recovers on its own, so one provider never stops the rest.