OPERATIONAL HEALTH
All Counsel.day services are operational.
A plain, honest account of how Counsel.day services are running right now. Each row below is one service; the table is auto-updated from internal monitoring every sixty seconds. Below the table, the last thirty days of incidents (which, at this stage of the product, is an empty record).
CURRENT STATUS BY SERVICE
Per-service operational health.
Service
What it does
Status
Surface 01
Marketing site
The public counsel.day pages, including this status page.
Operational
Surface 02
Application
The signed-in product: the evening vote, the dashboard, the verdict view.
Operational
Service 03
Authentication
Sign-in, sign-up, password reset, multi-factor authentication.
Operational
Service 04
Payments
Subscription billing, plan changes, invoicing. Processed in USD worldwide.
Operational
Service 05
Email delivery
Transactional email: invites, evening reminders, verdict notifications.
Operational
Service 06
Verdict pipeline
The analysis run that opens both verdicts and the five-layer synthesis on the final evening.
Operational
Service 07
Database
Primary Postgres, with row-level security and the sealed read path. Encrypted backups in two EU regions.
Operational
INCIDENT HISTORY · LAST 30 DAYS
Incidents in the last thirty days.
An incident is any time a customer-facing service was degraded or unavailable. We log every incident here within one hour of resolution, with a short write-up of what happened and what we changed.
No incidents recorded
No incidents in the past thirty days.
Status is auto-updated from internal monitoring. Subscribe to incident notifications at status.counsel.day (coming soon); for the moment, follow the changelog for any release-related downtime.