backupd_

Know when a database stops answering

backupd checks every database you connect every 5 minutes. When one stops answering, your team hears about it before your users do.

Start free trialSee pricing

app-prod

Checked every 5 minutes from outside your network.

Operational
Uptime
99.97%
Last 90 days
Response
38 ms
Connect time
Last check
2 min ago
Next in 3 min

Uptime

One bar per day, last 90 days

Up every day but one in the last 90 days

90 days ago1 outage, 14 minutesToday

Response time

Connect time per hour, last 24 hours

Between 30 and 60 ms all day

5 min
A check on every database.
90 days
Of uptime history kept.
No queries
Connection only, never a login.
Built in
Included on every plan.

What is checked

  • PostgreSQL, MySQL and MongoDB: a connection is opened to your host and closed. backupd never logs in to check uptime.
  • Convex: a request to your deployment’s version endpoint.
  • A check that takes more than 5 seconds counts as down.

Good morning

Acme · 4 databases, backed up on schedule.

Databases
4
3 active, 1 paused
Backups
2,317
711 this month
Storage
66.5 GB
Compressed size
Verified
98%
Restore tests passed

Recent backups

  • app-prod612 MBVerified12 min ago
  • billing88 MBSucceeded2 h ago
  • billingLost connection to serverFailed3 h ago
  • events1.4 GBVerified9 h ago

Needs attention

  • marketing-site is pausedNo backups for 3 days
  • billing failed onceThe next run succeeded

When it goes down

A Database unreachable alert goes to your channels with the error we saw, and the outage shows on the database’s uptime bar.

#ops-alerts

backupd APP 14:20

Database unreachable · billing

backupd couldn’t connect to billing.

Database
billing
Error
connect ETIMEDOUT
Open backupd

History you can show

Ninety days of checks, one bar per day, and connect time per hour for the last day, for every database in one place.

Activity

Every backup, restore test and change, newest first.

Today

  1. 09:00app-prod backed up612 MB · 41s
  2. 09:02app-prod passed a restore test5 of 5 tables, 1,766,383 rows
  3. 06:04billing backup failedLost connection to server during query
  4. 06:09billing backed upRetried on schedule, 88 MB

Yesterday

  1. 23:10events copied off-siteCopied to Cloudflare R2
  2. 14:31Ops team vault key addedBy Alex Kim

Where alerts go

Slack, Discord, Microsoft Teams, Telegram, email or a webhook. Pick the events each channel gets.

Notifications

Where backupd sends backup failures, storage limits, and billing alerts.

Add channel
  • Slack#ops-alertsBackup failedDatabase unreachableRestore test failed
  • Email[email protected]Storage limitBilling
  • Webhookhooks.acme.dev/backupdEvery event

Delivery log

Failed deliveries retry with exponential backoff for about an hour.

  • Backup failed · billingSlackDelivered06:04
  • Backup failed · billingWebhookDelivered06:04
  • Storage at 80%EmailDeliveredYesterday

Monitoring comes with your backups

Connect a database and its checks start straight away. Starter is free for 14 days.

Start free trialCompare plans