Previous incidents
Elevated Vrbo API Errors
Resolved Dec 28 at 03:17pm CET
This incident has been resolved.
2 previous updates
Elevated Vrbo API Errors resulting in an inability to connect some Vrbo accounts
Resolved Dec 22 at 09:25pm CET
We have implemented work around for the errors we saw from the Vrbo API, and the incident has now been resolved. Hospitable users can now reconnect their VRBO accounts reliably.
2 previous updates
Smartlock codes may be delayed.
Resolved Dec 22 at 05:16am CET
This issue has now been resolved.
3 previous updates
Elevated Vrbo API Errors
Resolved Dec 18 at 12:47pm CET
This incident has been resolved.
2 previous updates
Elevated Vrbo API Errors
Resolved Dec 15 at 05:26pm CET
This incident has been resolved.
2 previous updates
Elevated Vrbo API Errors
Resolved Dec 05 at 12:31am CET
This incident has been resolved.
3 previous updates
Delays in receiving updates from Airbnb
Resolved Oct 30 at 11:49pm CET
Further investigation confirmed that Webhook deliveries from Airbnb were delayed.
As a result, we saw delays in scheduled messages being sent to Airbnb guests, Airbnb reservations being delayed before appearing in Hospitable, and delays in receiving new messages from Airbnb guests.
The incident is now resolved.
1 previous update
Degraded application performance
Resolved Oct 24 at 12:45pm CEST
The third-party provider has confirmed resolution of the networking issue.
1 previous update
Elevated Vrbo API Errors
Resolved Oct 23 at 08:57pm CEST
This incident has been resolved.
1 previous update
Degraded application performance
Resolved Oct 14 at 03:06pm CEST
This incident has been resolved.
1 previous update
Elevated Vrbo API Errors
Resolved Oct 03 at 07:34pm CEST
This incident has been resolved.
If you do not see your Vrbo account reconnected, Vrbo may require you to reconfirm your 2-factor authentication. You can do that by going to Connected Accounts on Hospitable and Reconnecting your Vrbo account.
2 previous updates
Elevated Vrbo API Errors
Resolved Oct 03 at 02:11am CEST
This incident has been resolved.
2 previous updates