User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
booksy.com · Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1490 ms · 5 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 877 ms | 0 |
| 03:15 | 0 | 0.0 | 747 ms | 0 |
| 03:30 | 0 | 0.0 | 2063 ms | 0 |
| 03:45 | 0 | 0.0 | 1053 ms | 0 |
| 04:00 | 0 | 0.0 | 487 ms | 0 |
| 04:15 | 0 | 0.0 | 526 ms | 0 |
| 04:30 | 0 | 0.0 | 770 ms | 0 |
| 04:45 | 0 | 0.0 | 410 ms | 0 |
| 05:00 | 0 | 0.0 | 602 ms | 0 |
| 05:15 | 0 | 0.0 | 1173 ms | 0 |
| 05:30 | 0 | 0.0 | 577 ms | 0 |
| 05:45 | 0 | 0.0 | 912 ms | 0 |
| 06:00 | 0 | 0.0 | 594 ms | 0 |
| 06:15 | 0 | 0.0 | 971 ms | 0 |
| 06:30 | 0 | 0.0 | 729 ms | 0 |
| 06:45 | 0 | 0.0 | 879 ms | 0 |
| 07:00 | 0 | 0.0 | 874 ms | 0 |
| 07:15 | 0 | 0.0 | 630 ms | 0 |
| 07:30 | 0 | 0.0 | 720 ms | 0 |
| 07:45 | 0 | 0.0 | 698 ms | 0 |
| 08:00 | 0 | 0.0 | 992 ms | 0 |
| 08:15 | 0 | 0.0 | 1165 ms | 0 |
| 08:30 | 0 | 0.0 | 1657 ms | 0 |
| 08:45 | 0 | 0.0 | 927 ms | 0 |
| 09:00 | 0 | 0.0 | 618 ms | 0 |
| 09:15 | 0 | 0.0 | 890 ms | 0 |
| 09:30 | 0 | 0.0 | 261 ms | 0 |
| 09:45 | 0 | 0.0 | 1624 ms | 0 |
| 10:00 | 0 | 0.0 | 833 ms | 0 |
| 10:15 | 0 | 0.0 | 714 ms | 0 |
| 10:30 | 0 | 0.0 | 899 ms | 0 |
| 10:45 | 0 | 0.0 | 1388 ms | 0 |
| 11:00 | 0 | 0.0 | 264 ms | 0 |
| 11:15 | 0 | 0.0 | 679 ms | 0 |
| 11:30 | 0 | 0.0 | 687 ms | 0 |
| 11:45 | 0 | 0.0 | 540 ms | 0 |
| 12:00 | 0 | 0.0 | 874 ms | 0 |
| 12:15 | 0 | 0.0 | 1160 ms | 0 |
| 12:30 | 0 | 0.0 | 646 ms | 0 |
| 12:45 | 0 | 0.0 | 878 ms | 0 |
| 13:00 | 0 | 0.0 | 1010 ms | 0 |
| 13:15 | 0 | 0.0 | 662 ms | 0 |
| 13:30 | 0 | 0.0 | 1101 ms | 0 |
| 13:45 | 0 | 0.0 | 828 ms | 0 |
| 14:00 | 0 | 0.0 | 1490 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Booksy yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Booksy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Booksy alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Booksy is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Booksy's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.