Resly Outage History

Resly degraded · 1 active incident View live status →

Resly had 24 outages in the last 2 years totaling 2145h 17m of downtime — averaging 1 incident per month.

There were 24 Resly outages since January 7, 2025 totaling 2145h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://resly.statuspage.io

Minor April 24, 2026

Booking.com Guest Messages

Detected by Pingoru
Apr 24, 2026, 03:32 AM UTC
Resolved
Apr 24, 2026, 10:49 PM UTC
Duration
19h 16m
Affected: Booking.com
Timeline · 2 updates
  1. investigating Apr 24, 2026, 03:32 AM UTC

    Booking.com guest messages are currently not being received in Resly. We are currently investigating. Please check the booking.com extranet for guest messages.

  2. resolved Apr 24, 2026, 10:49 PM UTC

    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.

Read the full incident report →

Minor April 20, 2026

Agoda outage

Detected by Pingoru
Apr 20, 2026, 05:30 PM UTC
Resolved
Apr 20, 2026, 07:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 21, 2026, 01:38 AM UTC

    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.

Read the full incident report →

Critical April 10, 2026

Traveloka Outage

Detected by Pingoru
Apr 10, 2026, 04:10 AM UTC
Resolved
Apr 11, 2026, 03:05 AM UTC
Duration
22h 54m
Affected: Traveloka
Timeline · 2 updates
  1. investigating Apr 10, 2026, 04:10 AM UTC

    We are currently experiencing a Traveloka Outage and are investigating.

  2. resolved Apr 11, 2026, 03:05 AM UTC

    This outage has been resolved.

Read the full incident report →

Major April 9, 2026

Westpac Bank Feed pending transactions

Detected by Pingoru
Apr 09, 2026, 11:21 PM UTC
Resolved
Apr 12, 2026, 11:06 PM UTC
Duration
2d 23h
Affected: Westpac
Timeline · 2 updates
  1. investigating Apr 09, 2026, 11:21 PM UTC

    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.

  2. resolved Apr 12, 2026, 11:06 PM UTC

    This has ben resolved

Read the full incident report →

Critical March 25, 2026

NAB Bank Feed Delays

Detected by Pingoru
Mar 25, 2026, 04:11 AM UTC
Resolved
Mar 27, 2026, 07:47 AM UTC
Duration
2d 3h
Affected: NAB
Timeline · 5 updates
  1. identified Mar 25, 2026, 04:11 AM UTC

    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.

  2. identified Mar 26, 2026, 04:38 AM UTC

    We are continuing to seek updates regarding the NAB bank feed delays. It is still under investigation from the bank.

  3. identified Mar 27, 2026, 12:08 AM UTC

    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.

  4. identified Mar 27, 2026, 03:27 AM UTC

    A recent update from NAB indicates we are expecting a fix by close of business today.

  5. resolved Mar 27, 2026, 07:47 AM UTC

    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.

Read the full incident report →

Major February 17, 2026

NAB Bank Feed Outage

Detected by Pingoru
Feb 17, 2026, 11:02 PM UTC
Resolved
Feb 18, 2026, 10:42 PM UTC
Duration
23h 39m
Affected: NAB
Timeline · 2 updates
  1. identified Feb 17, 2026, 11:02 PM UTC

    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.

  2. resolved Feb 18, 2026, 10:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 17, 2026

Resly Pay Outage ( NZ Properties)

Detected by Pingoru
Feb 17, 2026, 01:18 AM UTC
Resolved
Mar 25, 2026, 04:09 AM UTC
Duration
36d 2h
Affected: Web App
Timeline · 4 updates
  1. identified Feb 17, 2026, 01:18 AM UTC

    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.

  2. monitoring Feb 19, 2026, 12:53 AM UTC

    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.

  3. monitoring Feb 25, 2026, 03:25 AM UTC

    Refund processing has been resolved. Some selected VCC's are still failing.

  4. resolved Mar 25, 2026, 04:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Bank Feed Delays

Detected by Pingoru
Nov 18, 2025, 12:39 AM UTC
Resolved
Nov 18, 2025, 03:09 AM UTC
Duration
2h 30m
Affected: ANZASBBank of QueenslandBendigo BankBNZCBA - CommBizCommonwealth BankMacquarie BankNABSuncorp GroupWestpac
Timeline · 2 updates
  1. investigating Nov 18, 2025, 12:39 AM UTC

    We are currently investigation an outage with the bank feeds. We will update as soon as possible once the bank feeds have been restored.

  2. resolved Nov 18, 2025, 03:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 13, 2025

CBA Bank Feeds

Detected by Pingoru
Nov 13, 2025, 10:54 PM UTC
Resolved
Nov 17, 2025, 12:37 AM UTC
Duration
3d 1h
Affected: CBA - CommBizCommonwealth Bank
Timeline · 2 updates
  1. identified Nov 13, 2025, 10:54 PM UTC

    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.

  2. resolved Nov 17, 2025, 12:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 21, 2025

CBA Bank Feed Delays

Detected by Pingoru
Oct 21, 2025, 06:19 AM UTC
Resolved
Oct 21, 2025, 10:58 PM UTC
Duration
16h 39m
Affected: CBA - CommBizCommonwealth Bank
Timeline · 2 updates
  1. investigating Oct 21, 2025, 06:19 AM UTC

    We are currently investigating delays to Bank Feeds on customers banking with Commonwealth Bank.

  2. resolved Oct 21, 2025, 10:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 16, 2025

Booking.com Reservations outage

Detected by Pingoru
Oct 16, 2025, 11:01 PM UTC
Resolved
Oct 19, 2025, 11:01 PM UTC
Duration
3d
Affected: Booking.com
Timeline · 2 updates
  1. monitoring Oct 16, 2025, 11:01 PM UTC

    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.

  2. resolved Oct 19, 2025, 11:01 PM UTC

    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."

Read the full incident report →

Major October 14, 2025

NZ ReslyPay Impacted Payouts

Detected by Pingoru
Oct 14, 2025, 11:07 PM UTC
Resolved
Oct 20, 2025, 02:03 AM UTC
Duration
5d 2h
Timeline · 4 updates
  1. monitoring Oct 14, 2025, 11:07 PM UTC

    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.

  2. monitoring Oct 15, 2025, 02:53 AM UTC

    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.

  3. monitoring Oct 16, 2025, 10:55 PM UTC

    The connectivity issue is still being investigated and the team are working to resolve as quickly as possible.

  4. resolved Oct 20, 2025, 02:03 AM UTC

    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.

Read the full incident report →

Critical September 16, 2025

Booking.com Outage

Detected by Pingoru
Sep 16, 2025, 02:15 AM UTC
Resolved
Sep 16, 2025, 11:09 PM UTC
Duration
20h 54m
Affected: Booking.com
Timeline · 2 updates
  1. investigating Sep 16, 2025, 02:15 AM UTC

    Booking.com are currently experiencing an outage. First appearing at 16/9 10.45am. They are working to resolve the issue as soon as possible. Bookings will not time out during this time however we recommend entering manually during the outage.

  2. resolved Sep 16, 2025, 11:09 PM UTC

    Booking.com have confirmed the issue has been resolved.

Read the full incident report →

Minor August 18, 2025

Bank Feeds - Bank of Queensland

Detected by Pingoru
Aug 18, 2025, 06:26 AM UTC
Resolved
Sep 16, 2025, 02:17 AM UTC
Duration
28d 19h
Affected: Bank of Queensland
Timeline · 4 updates
  1. investigating Aug 18, 2025, 06:26 AM UTC

    We are aware of delays to bank feed updates and this has been escalated to BOQ

  2. investigating Aug 18, 2025, 06:30 AM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 28, 2025, 12:21 AM UTC

    We are continuing to investigate this issue.

  4. resolved Sep 16, 2025, 02:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 12, 2025

BOQ Delays Bank Feed

Detected by Pingoru
Aug 12, 2025, 03:02 AM UTC
Resolved
Aug 15, 2025, 05:54 AM UTC
Duration
3d 2h
Affected: Bank of Queensland
Timeline · 3 updates
  1. investigating Aug 12, 2025, 03:02 AM UTC

    We are aware of delays to bank feed updates and this has been escalated to BOQ

  2. investigating Aug 12, 2025, 03:26 AM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 15, 2025, 05:54 AM UTC

    We have been advised that BOQ have resolved the issue. It may take some time for the delayed transaction to update"

Read the full incident report →

Critical June 12, 2025

Resly is currently unavailable

Detected by Pingoru
Jun 12, 2025, 08:30 PM UTC
Resolved
Jun 13, 2025, 02:05 AM UTC
Duration
5h 34m
Affected: Application Access / LoginWeb App
Timeline · 5 updates
  1. investigating Jun 12, 2025, 08:30 PM UTC

    We're currently experiencing an outage due to a global issue with Google Cloud services. This is affecting access to the Resly platform. We're monitoring the situation closely and will provide updates as soon as we have more information. Thanks for your patience.

  2. investigating Jun 12, 2025, 09:17 PM UTC

    We're currently experiencing an outage due to a global issue with Google Cloud services. This is affecting access to the Resly platform. Google have announced that they have identified the issue and are currently rolling out a fix. This will take some time for them to roll out worldwide. We're monitoring the situation closely and will provide updates as soon as we have more information. Thanks for your patience.

  3. investigating Jun 13, 2025, 12:02 AM UTC

    Some services are slowly starting to be restored. At this stage, New Zealand properties should now be able to access some areas of Resly as normal. However, users in Australia and Fiji may still experience service interruptions while restoration work continues.

  4. monitoring Jun 13, 2025, 01:47 AM UTC

    Google has now resolved their outage and DNS servers are coming back up worldwide which should allow most people to now access app.resly.com.au We'll continue to monitor access closely over the next few hours

  5. resolved Jun 13, 2025, 02:05 AM UTC

    Access to app.resly.com.au is now restored

Read the full incident report →

Minor February 17, 2025

Search bar not updating the reservation and unable to locate the new recent reservations created after 15/02/2025.

Detected by Pingoru
Feb 17, 2025, 01:38 AM UTC
Resolved
Feb 17, 2025, 05:09 AM UTC
Duration
3h 30m
Timeline · 3 updates
  1. investigating Feb 17, 2025, 01:38 AM UTC

    We are currently investigating the issue.

  2. monitoring Feb 17, 2025, 02:23 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 17, 2025, 05:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 23, 2025

Agoda Outage

Detected by Pingoru
Jan 23, 2025, 11:44 PM UTC
Resolved
Jan 24, 2025, 03:55 AM UTC
Duration
4h 11m
Affected: Agoda
Timeline · 2 updates
  1. investigating Jan 23, 2025, 11:44 PM UTC

    Agoda have notified us of a current outage impacting the delivery of bookings and cancellations. Please check the extranet and manually action any new bookings.

  2. resolved Jan 24, 2025, 03:55 AM UTC

    This outage has been resolved.

Read the full incident report →

Notice January 14, 2025

Suncorp Outage Resolved

Detected by Pingoru
Jan 14, 2025, 11:25 PM UTC
Resolved
Jan 14, 2025, 11:25 PM UTC
Duration
—
Affected: Suncorp Group
Timeline · 1 update
  1. resolved Jan 14, 2025, 11:25 PM UTC

    Suncorp Outage with Open banking has been resolved now.

Read the full incident report →

Notice January 9, 2025

Test 2

Detected by Pingoru
Jan 09, 2025, 09:20 PM UTC
Resolved
Jan 09, 2025, 09:25 PM UTC
Duration
4m
Timeline · 2 updates
  1. identified Jan 09, 2025, 09:20 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Jan 09, 2025, 09:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 9, 2025

Test incident

Detected by Pingoru
Jan 09, 2025, 09:15 PM UTC
Resolved
Jan 09, 2025, 09:19 PM UTC
Duration
3m
Timeline · 2 updates
  1. monitoring Jan 09, 2025, 09:15 PM UTC

    We are monitoring the situation and will update when we here more

  2. resolved Jan 09, 2025, 09:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 9, 2025

Test incident - please ignore

Detected by Pingoru
Jan 09, 2025, 08:49 PM UTC
Resolved
Jan 09, 2025, 09:03 PM UTC
Duration
14m
Timeline · 3 updates
  1. investigating Jan 09, 2025, 08:49 PM UTC

    We are currently investigating this issue.

  2. identified Jan 09, 2025, 08:56 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jan 09, 2025, 09:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 7, 2025

Test Incident 2 - With component connected

Detected by Pingoru
Jan 07, 2025, 10:49 PM UTC
Resolved
Jan 07, 2025, 10:54 PM UTC
Duration
5m
Timeline · 5 updates
  1. investigating Jan 07, 2025, 10:49 PM UTC

    This is just a test! We are checking on the incident process works when connected to a component

  2. identified Jan 07, 2025, 10:49 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 07, 2025, 10:50 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Jan 07, 2025, 10:51 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jan 07, 2025, 10:54 PM UTC

    This test incident has been resolved

Read the full incident report →

Notice January 7, 2025

Test Incident - not connected to any component

Detected by Pingoru
Jan 07, 2025, 10:48 PM UTC
Resolved
Jan 07, 2025, 10:54 PM UTC
Duration
5m
Timeline · 2 updates
  1. investigating Jan 07, 2025, 10:48 PM UTC

    Please note this is just a test ! Here is a description of said incident.

  2. resolved Jan 07, 2025, 10:54 PM UTC

    This incident has been resolved.

Read the full incident report →