Edge & app runtime
Marketing site, dashboard, and server functions run on Cloudflare Workers.
Operational guidance
ValidReach service status
This page explains platform components and self-checks. It is not a live multi-region status feed. If something looks wrong, use the checks below or contact us.
Systems
What powers ValidReach
Verification API
POST /api/v1/verify and batch endpoints authenticate with API keys and return structured results.
Data store
Account, session, credit, and job metadata are stored in Cloudflare D1 via Drizzle.
List jobs
Bulk verification jobs process asynchronously; track progress under Dashboard → Lists.
Self-check
Before you assume an outage
HTTP status codes
401: missing or invalid API key. 402: insufficient credits. 400: bad request body. 5xx: possible upstream issues — retry with backoff.
Result = unknown
Unknown is a valid outcome when classification is not definitive. It does not mean the API is down, and unknown is not billable.
Dashboard history
Review recent checks and batch jobs in History and Lists. Failed jobs surface errors when processing could not complete.
Account-specific issues
Credit balance, key permissions, and input quality can look like outages. Confirm keys under Settings and balance under Credits.