Uptime and reliability

How Booked stays up, and what happens when a dependency does not.

If the database is slow or unavailable, booking pages still load, but there is no automatic failover. There is no uptime SLA on the current plans. The Terms say Booked targets high availability but does not guarantee uninterrupted service (Terms, section 11).

What can degrade

Booked depends on external providers for card processing (Stripe), email (Resend), and SMS (a licensed gateway). Outages at those providers can affect the parts of Booked that use them:

If this is downThis still works
StripeBookings without deposits still complete; deposit-required bookings pause
Email gatewayBookings still complete; confirmation emails queue for later delivery
SMS gatewayBookings still complete; SMS reminders retry on the next window

The principle behind that table

Taking the booking is the thing that must not fail. Every dependency is arranged so that a failure downstream of the booking (a message, a receipt) degrades into a delay rather than a lost appointment. The one exception is a deposit, because a booking that was supposed to take money and did not is worse than no booking.

What an outage does not do

It does not lose a booking that was already confirmed, and it does not double-book one. Availability is decided in the database inside the same transaction that writes the booking, so an interruption either commits the whole booking or none of it.

Data durability

Database backups are managed by Supabase and taken at least once a day.

If something is wrong right now

Email hello@booked.co with "URGENT" in the subject and the shop URL. A live booking problem is prioritised over everything else: see Support and response times.

More in Evaluating Booked