OwnerRez Outage History

Booking.com stopped sending guest phone numbers on September 29. OwnerRez requires a phone number to save a card, so Booking.com cards are being rejected with "Missing card info: Phone Number". Fix is in progress.

The fix is deployed. OwnerRez no longer requires a phone number to save a Booking.com card, so new bookings are coming through with the card attached instead of being rejected with "Missing card info: Phone Number". We're monitoring new bookings to confirm. Bookings rejected between September 29 and the fix won't recover on their own — contact support for any other help.

Some people are experiencing problems with our hosted websites right now. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

We're currently having issues with processing WhatsApp messages from username-only senders. WhatsApp is rolling out a new feature where users can be referenced by a username-only and no longer require a phone number. This feature is new and changes how we have to ingest and process WhatsApp webhooks. Messages from WhatsApp users who only have a username are not being processed by OwnerRez, and not showing up in the inbox. We're so sorry about that. We are working on implementing the necessary changes, so please standby for further updates.

Over the past couple of hours many users have experienced app slowdowns. We think we've solved the underlying issue, and the app should now be recovering. You may see a captcha when logging into the site over the next couple of days as a result of our fix.

Booking.com is currently experiencing an outage with their Reservation APIs, which is disrupting the flow of reservation data into OwnerRez. We are investigating, and will update this notice as we find out more.

GuestSmiles is experiencing an outage on their website and API endpoints due to a network issue at their hosting provider. This is preventing availability and rate updates from reaching GuestSmiles listings. We have temporarily paused pushes to GuestSmiles on our end to prevent repeated errors. Once GuestSmiles resolves the issue and confirms service is restored, we will re-enable syncing and trigger a full push to bring all listings up to date.

Some people are experiencing problems with Vrbo Channel Bridge. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

Some people are experiencing problems with our service right now around processing Stripe, and potentially other payment methods that involve fees, with the error "A expense vendor setting does not exist for this key." We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

We've fixed the core issue. Please try any failures again, and reach out to support if you continue to have any issues.

Since approximately 20:15 UTC, Booking.com has reported a known outage with their reservation API. Reservations from Booking.com may not be coming into OwnerRez. We are monitoring it, and will advise once we hear that the issue is resolved on their end.

We're seeing all reservation API endpoints return consistently successful responses.

We are seeing an increased delay in Rezzy generating messages due to a service outage from one of our vendors. We are monitoring this outage.

Our vendor has implemented a fix and we are monitoring the results.

We're aware that some Airbnb calendars are showing as fully blocked. We're actively investigating and we'll have an update shortly. We apologize for the inconvenience.

We have resolved the issue and availability is being restored. Everything should return to normal shortly. We appreciate your patience and apologize for the inconvenience.

We're aware of an increase in webhook delays for integrated oauth applications. We researching this incident.

We've fixed the core issue, and webhook delay is returning to normal thresholds.

We're aware of some errors encountered on the inbox. We have identified the cause and we are working on a correction.

We've fixed the core issue, and are waiting for things to recover.