Uptime and protocol monitoring from seven regions, an email-health suite most monitors don't have, alerting that escalates instead of nagging, status pages people can follow, teams, and an API your pipeline can drive. Free covers a lot of it; the Pro badge marks what doesn't.
Every check runs from London on Free and from all seven regions on Pro — North Virginia, Oregon, São Paulo, Singapore, Sydney and Tokyo — so you see the internet the way your visitors do, not the way your server does.
HTTPS and HTTP checks with response codes, connect and time-to-first-byte timing. Require an exact status code, a keyword the page must contain, or one it must not — so a maintenance page returning 200 counts as down.
SSH, FTP, IMAP, POP3, MySQL and MariaDB, PostgreSQL and Redis. UpConduit connects, reads the service greeting or handshake, confirms the right protocol answered, and records the version it reports.
An sshd or database that changes version when nobody upgraded it is worth knowing about. Service banners are compared check to check and you're told once when they change.
Resolve A, AAAA, CNAME, MX, TXT or NS for any name, optionally require an expected value, and get told when the answer changes.
Expiry warnings at 30, 15 and 7 days, plus detection of outdated protocols and weak ciphers on the negotiated handshake.
Registration-expiry warnings at 60, 30, 14 and 7 days, and an alert when a domain's nameservers change.
Your scheduled job pings a private URL. Silence beyond the expected interval becomes the alert — the only way to monitor something that runs at 3am.
Subscribe to the published status of AWS, Azure, Google Cloud, Cloudflare, GitHub, Stripe, OpenAI, Vercel, Netlify and DigitalOcean and get their incidents on your channels. Tag a monitor with what it runs on and a down alert says whether the provider is having trouble too.
On-demand and continuous delivery tests: DNS, connect, TLS, time to first byte, page weight, compression, caching, HTTP/2 and HTTP/3, with plain-English fixes. Three tests a day on Free, fifty on Pro.
Your endpoints placed where they really are, every probe route drawn and coloured by its median latency. The picture of your service that no table gives you.
The suite that turns a monitoring tool into something a whole business relies on. Included on every plan.
MX presence, SPF validity, DKIM key status including provider key-rotation quirks, DMARC presence and policy strength — checked continuously, not once.
Records that are still technically valid but changed since last check. An unexpected SPF or MX edit is how deliverability quietly breaks, and most tools only check validity.
DNS blocklist checks with canary validation, so a list that has gone silent is never mistaken for a clean result.
Connects to your mail exchanger, reads the banner and confirms STARTTLS is offered.
One blip never pages you. Down requires consecutive confirmed failures, recovery alerts once, and a single region owns alerting so a global network never duplicates bad news.
Branded email and webhooks for Slack, Discord, Microsoft Teams or generic JSON on every plan. SMS for downtime and recovery on Pro, fifty a month.
Open an incident when a monitor goes down or gets slow and close it automatically on recovery. Only pages go to your incident tool; drift, certificate and reminder alerts stay on email.
"Alert if slower than 2 seconds." Three consecutive slow checks before you hear about it, three fast ones before it's called recovered — one slow request is weather, three is climate.
Off by default. Turn it on and you're re-alerted every 10, 30, 60 or 240 minutes until it recovers — by email and webhook, never burning your SMS allowance.
Still down after 10 minutes? Email the on-call engineer. After 30, text the lead. Up to three ordered steps, each firing once per outage, and everyone who was pulled in hears when it recovers. SMS steps on Pro.
When a monitor tagged "runs on AWS" goes down while AWS is reporting an incident, the alert says so. Is it us or them, answered in the alert itself.
Mail records, nameservers, service versions, DNS answers, weak TLS, performance regressions: each alerts once when it changes, then stays quiet.
One-off or weekly, in your timezone, for all monitors or a chosen few. Covered monitors pause, count no downtime, and resume the moment the window closes — so a deploy that leaves something broken still pages you.
Group monitors by client, environment or team. Filter every view by tag; scope maintenance windows to a tag's worth of monitors.
Every monitor with latency history, certificate days, email health and recent events, refreshed as the probes report in. Built for a phone as much as a desk.
Per monitor per day: checks, uptime, incidents, average and worst latency, kept for thirteen months and available through the API. A full reporting module is being built on top of it.
A public page at upconduit.io/s/your-name, showing component names, states and 24-hour uptime — never targets, latencies or error text.
Post an incident — investigating, identified, monitoring, resolved — with updates as you learn more. Open incidents and the last 30 days of resolved ones appear on the page.
Visitors subscribe by email with confirmed opt-in. They're told when a component goes down or recovers and on every incident update. Your status page becomes the place people go instead of your inbox.
Everything the dashboard does, your pipeline can do. Read the API docs.
API keys on every plan, read-only or read-write, shown once and stored hashed. Monitors, maintenance windows, daily uptime data. 60 requests a minute per key.
A uc command line, JavaScript and Python SDKs, and a Terraform provider for monitoring as code — declare a monitor in the same repo as the thing it watches.
Open a 20-minute maintenance window before a release and let it close itself. Register a monitor for every preview environment and delete it on merge.
Generate a client in any language from openapi.json.
Invite colleagues into one account. Editors add and change monitors and settings; viewers see everything and change nothing. Billing, API keys and the team itself stay with the owner.
Whoever adds a monitor, alerts go to the account's channels — no orphaned monitors emailing someone who left.
Free is a real plan, not a trial. Pro is £12 a month or £120 a year.
| Free | Pro | |
|---|---|---|
| Monitors | 10 | 50 |
| Check interval | 5 minutes | 1 minute |
| Probe regions | London | All 7 |
| All monitor types, email health, drift alerts | ✓ | ✓ |
| Email and webhook alerts, reminders, thresholds | ✓ | ✓ |
| Escalation policies | email steps | email + SMS steps |
| SMS alerts | — | 50 / month |
| Maintenance windows, tags | ✓ | ✓ |
| Status page with incidents and subscribers | ✓ | ✓ |
| Speed tests | 3 / day | 50 / day |
| API, CLI, SDKs, Terraform | ✓ | ✓ |
| Team members | — | up to 10 |
No card, no trial clock. Upgrade when you want the global network, minute checks or your team in the account.