System status
This page reports the live, machine-measured operational status of Conduit: current health for every customer-facing component, daily uptime for the last 90 days, and every incident since monitoring began. It is generated from automated checks and is never edited by hand.
All systems operational
Every component below is passing its checks.
Last checked 2026-09-08 06:31 UTC · checks run every 15 minutes
What's measured, piece by piece
Each component is derived from the services that actually carry it — the vendor chips underneath show the raw inputs. The rightmost bar cell is today, filling in live as each 15-minute check lands; gray cells are days before monitoring existed and are never counted as uptime. Monitoring publicly since August 26, 2026 — day 14 of the 90-day history, building in the open.
Phone answering
Inbound calls reaching the AI assistant and being answered.
Twilio (telephony) reports a minor issue on their own status page; our direct checks are passing.
Text messaging
Missed-call text-back, confirmations, and two-way texting.
Twilio (telephony) reports a minor issue on their own status page; our direct checks are passing.
Web dashboard & API
conduitapp.ai, the owner dashboard, and the APIs behind them.
Supabase (database) reports a minor issue on their own status page; our direct checks are passing.
AI processing
The language-model layer behind conversations and summaries.
Email notifications
Owner notifications, briefings, and account email.
Billing & checkout
Subscription checkout and the billing portal.
Incident history
Opened and resolved by the same automated checks that power the rest of this page — an outage can't be quietly left out.
Web dashboard & API
Resolved · 136 minvendor status: major Affected dependency: Supabase (database).
2026-09-04 01:01 UTC → 2026-09-04 03:17 UTC
Web dashboard & API
Resolved · 90 minvendor status: major Affected dependency: Supabase (database).
2026-09-01 09:15 UTC → 2026-09-01 10:45 UTC
Why you can trust this page
Measured, not declared
Every state on this page comes from an automated check. There is no admin button that sets a component green.
No fabricated history
Uptime bars begin the day measurement began. A gray cell means “not measured,” and it never counts as up.
Stale data can't look green
If the monitoring pipeline itself stops reporting, everything here downgrades to “unverified” within 45 minutes.
Verify it yourself
The exact data behind this page is public: machine-readable JSON and an Atom feed of incidents, linked below.
How this page stays honest
How is this status measured?
Automated checks run every 15 minutes: each vendor's public status feed is read, authenticated connectivity probes verify Conduit can actually reach the services it depends on, and the platform's own public health endpoint is probed. Component status is the worst of its inputs. There is no hand-editable status anywhere in the pipeline — nobody can paint this page green.
What does “degraded” mean?
It means our own measurements found impairment: a direct check answered slower than 2.5 seconds, or a vendor declared a major platform outage while our checks still pass. “Outage” means our checks are failing outright. “Unverified” means we currently have no trustworthy data — shown honestly instead of assuming everything is fine. In the daily bars, red is reserved for sustained downtime (more than an hour's worth of failed checks in a day); a brief blip colors the day amber, and every cell's tooltip carries the exact measured percentage either way.
Why do I sometimes see a vendor advisory under an operational component?
Vendors publish global status pages covering their whole platform, and a “minor issue” there often affects a region or sub-service we don't touch. We measure our own slice directly with authenticated checks, so when a vendor reports a minor issue but our measurements pass, the component stays operational and the advisory is disclosed underneath — we report what we measure, in both directions.
Why does the uptime history start on a specific date?
The bars show only days we actually measured — public monitoring began on August 26, 2026. Days before monitoring existed are shown as “no data,” never backfilled or estimated. The rightmost cell is today: it fills in live as each 15-minute check lands, then becomes a permanent history row when the day ends (UTC). A 90-day uptime number appears only once 90 days have genuinely been recorded.
What happens when something breaks?
Two consecutive failed checks open an incident automatically: it appears on this page, the team is alerted immediately, and the recovery is recorded by the same automated checks. The incident history below is machine-written — an outage cannot be quietly left out.
Is Conduit monitored from outside its own infrastructure?
Yes. An independent external monitor (Better Stack) probes Conduit from outside our infrastructure and its signal feeds the “Conduit platform” status on this page — an outside witness our own systems can't influence.
Something looks wrong for my account — where do I report it?
Use the contact page or email support@conduitapp.ai. This page tracks platform-wide health; account-specific issues (a forwarding change at your carrier, a paused assistant) won't appear here but the support team will see them with you.
Every number on this page is machine-measured and refreshes automatically — nothing is entered by hand. Monitoring since August 26, 2026.