User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 47 min ago. Last stored result reached it in 380 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 809 ms | 0 |
| Mon 16 | 0 | 0.0 | 187 ms | 0 |
| Mon 18 | 0 | 0.0 | 156 ms | 0 |
| Mon 20 | 0 | 0.0 | 146 ms | 0 |
| Mon 22 | 0 | 0.0 | 220 ms | 0 |
| Tue 00 | 0 | 0.0 | 144 ms | 0 |
| Tue 02 | 0 | 0.0 | 117 ms | 0 |
| Tue 04 | 0 | 0.0 | 230 ms | 0 |
| Tue 07 | 0 | 0.0 | 359 ms | 0 |
| Tue 09 | 0 | 0.0 | 150 ms | 0 |
| Tue 11 | 0 | 0.0 | 129 ms | 0 |
| Tue 13 | 0 | 0.0 | 166 ms | 0 |
| Tue 15 | 0 | 0.0 | 129 ms | 0 |
| Tue 17 | 0 | 0.0 | 136 ms | 0 |
| Tue 20 | 0 | 0.0 | 339 ms | 0 |
| Tue 22 | 0 | 0.0 | 275 ms | 0 |
| Wed 00 | 0 | 0.0 | 188 ms | 0 |
| Wed 02 | 0 | 0.0 | 108 ms | 0 |
| Wed 05 | 0 | 0.0 | 104 ms | 0 |
| Wed 07 | 0 | 0.0 | 119 ms | 0 |
| Wed 09 | 0 | 0.0 | 836 ms | 0 |
| Wed 11 | 0 | 0.0 | 590 ms | 0 |
| Wed 14 | 0 | 0.0 | 211 ms | 0 |
| Wed 16 | 0 | 0.0 | 202 ms | 0 |
| Wed 18 | 0 | 0.0 | 203 ms | 0 |
| Wed 20 | 0 | 0.0 | 179 ms | 0 |
| Wed 22 | 0 | 0.0 | 143 ms | 0 |
| Thu 00 | 0 | 0.0 | 136 ms | 0 |
| Thu 03 | 0 | 0.0 | 801 ms | 0 |
| Thu 05 | 0 | 0.0 | 248 ms | 0 |
| Thu 07 | 0 | 0.0 | 232 ms | 0 |
| Thu 09 | 0 | 0.0 | 818 ms | 0 |
| Thu 11 | 0 | 0.0 | 355 ms | 0 |
| Thu 13 | 0 | 0.0 | 245 ms | 0 |
| Thu 15 | 0 | 0.0 | 326 ms | 0 |
| Thu 17 | 0 | 0.0 | 191 ms | 0 |
| Thu 19 | 0 | 0.0 | 802 ms | 0 |
| Thu 21 | 0 | 0.0 | 198 ms | 0 |
| Thu 23 | 0 | 0.0 | 732 ms | 0 |
| Fri 01 | 0 | 0.0 | 199 ms | 0 |
| Fri 04 | 0 | 0.0 | 672 ms | 0 |
| Fri 06 | 0 | 0.0 | 209 ms | 0 |
| Fri 08 | 0 | 0.0 | 136 ms | 0 |
| Fri 10 | 0 | 0.0 | 746 ms | 0 |
| Fri 12 | 0 | 0.0 | 213 ms | 0 |
| Fri 14 | 0 | 0.0 | 608 ms | 0 |
| Fri 16 | 0 | 0.0 | 130 ms | 0 |
| Fri 18 | 0 | 0.0 | 591 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for ReservationKey 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 ReservationKey goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ReservationKey alerts to Slack, Discord or a webhook — free.
We track ReservationKey (reservationkey.com) as part of the Money group. Reservation software for hotels, vacation rentals, campgrounds, and more. Manage bookings, payments, channels, and guest communication in one easy-to-use platform.
ReservationKey publishes an official status page at status.reservationkey.com; when we can read it, its incident level is folded into the status shown here.
Common problems for money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 398 ms average, 97–802 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public ReservationKey incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
398 ms on average over the last 24 hours (97–802 ms).
Yes, at https://status.reservationkey.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report ReservationKey here at once, the problem is on ReservationKey's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with ReservationKey. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.