System Status
Last checked: May 13, 2026 at 10:20 PM UTC · 5,608 checks logged
Current Status
Uptime
Performance over the last 90 days
Response Time
Measured from conduyt.com to conduyt.app every 5 minutes
Recent Incidents
We identified and resolved elevated p99 latency affecting API requests routed through US-West. Root cause was a connection pool saturation during a scheduled database maintenance window. No data was lost.
Some outbound webhooks experienced delivery delays of up to 90 seconds due to a queue backlog. The issue self-resolved after autoscaling provisioned additional worker capacity. We have since lowered the scaling threshold to prevent recurrence.
Get notified of incidents
We will only email you when something changes. No marketing, no spam.
How Conduyt monitors and reports system status
The dashboard above pulls from real production monitoring rather than a hand-edited status page. Conduyt operates a 24/7 monitoring stack that watches every customer-facing service — the web application, the REST API, the MCP server, the automation runner, the email and SMS dispatchers, the dialer, and the integration webhooks. Health checks run every 30 seconds against each service, and the results flow into the dashboard you see above with sub-minute latency.
Service uptime over the trailing 90 days is reported per service rather than as a single site-wide percentage. The reason is that a slow API hour matters to the team building integrations but doesn't necessarily affect a sales rep using the web app, and we'd rather show the truth per service than smooth it into one number. Our published service-level target is 99.9% monthly availability on each service; recent quarters have run at 99.98% or better across the board.
What counts as an incident
An incident is any condition that affects customer use of the platform: a service returning errors, a service responding too slowly to be usable, or a dependency outage that breaks a feature even if our infrastructure is healthy. We classify incidents into four severity levels based on customer impact, not technical root cause.
Severity 1 (Critical): Customers cannot use the platform for its primary purpose. Web app down, API unreachable, authentication broken. Pages every on-call engineer within 60 seconds; status page updated within 5 minutes; customer email notification within 30 minutes.
Severity 2 (Major): A core feature is broken or significantly degraded. Examples: automations not firing, scheduled email not sending, integration webhooks failing. Pages on-call within 5 minutes; status update within 15 minutes; customer notification within an hour if the issue persists.
Severity 3 (Minor): A non-core feature is degraded or a workaround exists. Reporting export delayed, a specific dashboard widget showing stale data. Pages within 15 minutes; status update within 30 minutes during business hours.
Severity 4 (Maintenance): Scheduled work with known customer impact. Database migrations, infrastructure upgrades, planned dependency updates. Announced in advance via status page and customer email.
Subscribing to status updates
If you operate workflows that depend on Conduyt being available — automated reports that fire on a schedule, integrations that push data into Conduyt from upstream systems, customer-facing features that pull from the Conduyt API — you should subscribe to status updates through the form above. Subscribers receive email notifications when incidents are declared and when they resolve.
For programmatic monitoring, we publish a JSON status endpoint at https://conduyt.com/status.json that returns current service-by-service status without requiring authentication. The endpoint is designed to be polled by your own monitoring infrastructure (Datadog, PagerDuty, custom scripts) so you can route Conduyt-related alerts through the same channels you use for your own services. Poll frequency: once every 60 seconds or slower; the endpoint is cached at the edge and won't return more frequent updates regardless of how often you query it.
Historical uptime and post-incident reviews
The dashboard above shows current status and 90-day uptime per service. For material incidents — anything classified as Severity 1 or Severity 2 — we publish a written post-incident review covering the timeline, the root cause, the customer impact, the immediate remediation, and the longer-term prevention measures. Reviews typically appear within two weeks of resolution and are linked from the corresponding incident entry on this page.
Customers with a Business Associate Agreement (BAA) for HIPAA-applicable workflows receive enhanced incident reporting with breach-notification timelines scaled to the BAA terms. The standard 24-hour customer notification window tightens significantly for HIPAA-applicable incidents, and the post-incident review includes the specific BAA-required elements rather than just the general format.