Resly had 19 outages in the last 2 years totaling 2507h 26m of downtime — averaging 0.8 incidents per month.
There were 19 Resly outages since October 14, 2025 totaling 2507h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.
We’re aware of the “Undefined” error currently appearing when attempting to send emails from Resly. This has been raised with our engineering team and is currently being investigated.
The issue is now resolved
This is now resolved
We’re aware that some customers are currently seeing error messages related to Google connectivity. This is due to a service degradation on Google’s end. Our team is monitoring the situation. While these errors may appear within Resly, they are not impacting rates or causing overbookings, and no action is required from you at this stage. We’ll continue to monitor the issue and provide an update if anything changes. Thank you for your patience while Google works to restore normal service.
We are continuing to monitor for any further issues.
This has now be resolved. Any future errors will need to be raised and investigated. Thank you
We are aware that some ReslyPay payouts are currently delayed. We have raised this with our partners who are experiencing a temporary processing issue with their upstream processor that has slowed fund settlements. We are actively escalating and expect payouts to be released tomorrow Thursday 13th August.
We are continuing to monitor for any further issues.
This is no resolved and payouts have resumed.
We are aware of an issue impacting new property creation unavailable since Jun 28, 12:30 CEST with Booking.com and are monitoring their status page for updates. We have been advised to hold new property submissions for the time being. Any listings that have been published that haven't gone live during the outage will need to be republished.
Booking.com have now resolved this issue. We apologise for any inconvenience this may have caused. Action required: Please resend all failed requests during the outage.
We’re aware of an issue affecting image uploads and are working to resolve it. Thank you for your patience.
This has been resolved
Agoda experienced an outage from around 8:00 PM last night, which may have impacted booking and update delivery. We've completed a full sync and are currently re-pushing inventory and availability to Agoda; in the meantime, we recommend manually adding any missing bookings to ensure accuracy.
Missing bookings are now beginning to be automatically delivered. Please continue to monitor carefully.
The Agoda outage has now been resolved and bookings are being delivered. If you experience any edge cases with an Agoda booking please email [email protected] for further investigation.
We are currently experiencing a delay with Westpac transactions and are investigating.
We are continuing to investigate this issue.
This has been resolved please continue to monitor and report back if any further issues.
Booking.com guest messages are currently not being received in Resly. We are currently investigating. Please check the booking.com extranet for guest messages.
Booking.com has resolved an issue that caused some messages to remain in a pending state. The fix was deployed at 16:30 CEST, and all affected messages have now been successfully delivered. No notifications were lost. They are continuing to monitor the system closely, and no further issues have been observed since the fix was released.
Agoda reservation outage Reservations created by Agoda were not being sent through. Agoda have resolved this outage at 9:35pm (+10GMT) on the 20th of April. Any reservations made on Agoda during this time will need to be manually created in Resly.
We are currently experiencing a Traveloka Outage and are investigating.
This outage has been resolved.
We are aware of an issue impacting Westpac bank feeds. This has been raised this with our open banking partner for further investigation and resolution.
This has ben resolved
We have been made aware that NAB has recently experienced an issue impacting data-sharing capabilities, first identified on 22 March 2026. This has been escalated directly with their team, and they are actively working towards a resolution. We will continue to monitor the situation closely and keep you updated on any progress.
We are continuing to seek updates regarding the NAB bank feed delays. It is still under investigation from the bank.
We are continuing to seek updates regarding the NAB bank feed delays. It is still under investigation from the bank. We hope to have a more detailed update shortly.
A recent update from NAB indicates we are expecting a fix by close of business today.
NAB has now rolled out a fix, and your bank feed should begin updating shortly. Please allow up to an hour for all data to sync, and then refresh your bank feed. We’ll continue to monitor the situation and keep you updated. Thank you.
We have been made aware of an issue impacting NAB users. The issue had been identified as a recent update on NABs side has blocked requests to endpoints. This is being worked on as a priority.
This incident has been resolved.
The Outage is currently Impacting ReslyPay New Zealand clients with two separate payment flows: • Charging Selected VCC transactions • Refund processing We are currently work on getting this resolved with urgency.
VCC charging has been resolved apart from Agoda VCC's. There is still a 24 hour delay for charging Agoda cards expecting to be resolved by Friday afternoon.
Refund processing has been resolved. Some selected VCC's are still failing.
This incident has been resolved.
We are currently investigation an outage with the bank feeds. We will update as soon as possible once the bank feeds have been restored.
This incident has been resolved.
We are aware that bank feeds connected via CBA are currently unable to fetch data. CBA have advised that they are actively investigating and will provide an update as soon as practicable. We will share more information as it becomes available.
This incident has been resolved.
We are currently investigating delays to Bank Feeds on customers banking with Commonwealth Bank.
This incident has been resolved.
We have been made aware that booking.com is experiencing an outage that is affecting our Reservations API service. This issue first appeared at 2025-10-16, 11:10:26 AM UTC. They are working on resolving this issue as soon as possible. As an immediate mitigation, booking.com will apply a global hold to make sure that reservations will not timeout during this outage. They will stop the hold once the outage is over.
A message from booking.com "A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused."
Thank you for your incredible patience as we address a temporary issue impacting your payouts. We’ve worked with our merchant provide and have identified a connectivity outage with BNZ, our trusted partner for NZ merchant settlements, causing a brief delay in processing your funds. This issue is due to intermittent connection drops between our systems and BNZ’s, which is preventing payouts from settling as planned. Please rest assured that your funds are completely safe and secure, ready to be processed once this is resolved. Our merchant development team has pinpointed the root cause, and our CTO is directly overseeing this, making it our top priority. We’re working closely with BNZ to fix this urgently, and we’re fully committed to getting your payouts back on track. Thank you again for your understanding.
Some payments have successfully processed today after a stable connection was established. Our development team is closely monitoring the remaining payouts and working to ensure they are pushed through as quickly as possible.
The connectivity issue is still being investigated and the team are working to resolve as quickly as possible.
We are aware that the connection issue has now been resolved, and have been informed that most payouts were cleared on Friday the 17th. We are aware some payouts remain pending for October 15th and 16th, these are being closely monitored.