Skip to content

Live Checked ()

All systems operational.

Everything is running normally. Our checks run every minute from Europe, North America and Asia-Pacific.

99.96% measured over 90 days, average of eight services22 days without disruption

Services

Club OS99.93% · Realtime not measuredRealtime not measured Last 90 days: 9 disrupted days. 99.93% Operational
Sign-in99.93% · 90 days Last 90 days: 2 disrupted days. 99.93% Operational
Booking and meetings99.93% · Booking AvailabilityMeasured: Booking Availability Last 90 days: 7 disrupted days. 99.93% Operational
Email and notificationsReported by Resend · Notifications not measuredNotifications not measured Reported by Resend No percentage: not measured by us Operational
PaymentsReported by Stripe Reported by Stripe No percentage: not measured by us Operational
Public sites99.99% · 90 days Last 90 days: 0 disrupted days. 99.99% Operational

Recent history

Last 90 days
  • Failed checks for up to 9 minutes

    Club OS, Sign-in, Booking and meetings · some checks hit the 6-second timeout

  • Slow responses

    Club OS · slowest 5% of checks in the day’s last hour up to 2,127 ms

  • Failed checks for up to 73 minutes

    Club OS, Sign-in, Booking and meetings

Days are classed by what our checks measured.All 9 in incident history

Subscribe to updates

Today, the RSS feed carries incident updates and webhooks carry status changes. Email confirms your address only: incident emails are not sent yet. Unsubscribe anytime.

One email to confirm, then only incident notices. See our privacy policy.

How to read this page

Three kinds of evidence
Measured
We check it ourselves every minute from Europe, North America and Asia-Pacific. Each bar is one day; a coloured bar is a disrupted day.
Reported by a provider
The provider’s own status page, repeated here with a link to the source. We do not measure these, so they carry no percentage.
Not measured directly
Inferred from the services it runs on. We never call these operational; when nothing is wrong we say no known issue.

A minute counts as failed when the check failed in two or more of our three regions. The 99.96% figure is the share of minutes that did not fail, averaged over the eight services we measure, for the last 90 days. A row’s percentage is its lowest measured service; what we do not measure is not in it.

A day is disrupted when a measured service failed in two or more regions for 5 minutes or more, failed in one region for 30 minutes or more, or when its slowest 5% of checks took more than twice their usual time. Shorter failures leave the day’s bar calm.

Your own experience may differ. Monthly figures are in uptime reports, and every field is described in the API documentation.