Bond Trials Docs

System status

Live health of every service Bond depends on

Bond depends on a number of third-party services - AI providers, telephony, scheduling, storage, and infrastructure. The System Status page gives a live view of every service's health, along with a 90-day uptime history for each one. You don't need to be signed in to view it.

Monitored services

The following services are tracked and displayed on the status page:

Bond Trials - the application and its Aurora Postgres database, checked with a live probe from inside our network.
OpenAI - powers protocol parsing, trial matching, and agent system prompt generation.
LlamaIndex (LlamaParse) - extracts structured data from protocol PDFs.
ElevenLabs - provides AI voices and drives outbound prescreening calls.
Twilio - carrier for phone number provisioning and outbound call routing.
CRIO - the site's calendar for screening visit availability and booking.
AWS S3 - stores protocol documents and the parsed-protocol cache.
Sentry - captures and reports application errors.

Status indicators

Each service is shown with one of four indicators:

Operational - the service is reporting no issues.
Degraded - the service is experiencing reduced performance or a minor incident.
Partial outage - some functionality is unavailable.
Major outage - the service is broadly down.

Unknown status

If Bond can't reach a service's status feed, that service shows as Unknown rather than Operational - so a quiet failure in our monitoring doesn't look like a clean bill of health.

Uptime history

Below each service, a 90-day bar chart shows one bar per day coloured by the worst indicator seen that day. Hovering a bar shows the date and uptime percentage. The overall uptime percentage next to the service name is the average across the full 90-day window.

Status snapshots are captured every 30 minutes by a background job, so the history chart fills in automatically even when no one is viewing the page.