tag:status.basiq.io,2005:/historyBasiq Status - Incident History2024-03-29T18:51:32+11:00Basiqtag:status.basiq.io,2005:Incident/197091172024-01-29T13:03:59+11:002024-01-29T13:04:00+11:00CDR Data Fetching Issue Post-31 December 2023<p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>13:03</var> AEDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>13:34</var> AEDT</small><br><strong>Monitoring</strong> - We are pleased to inform you that the recent issue in fetching new transactions post-31 December 2023 has been successfully resolved.<br /><br />As of now, all transactions, including those posted between 31 December 2023, and 15 January 2024, are available and accessible. The Data Holders have implemented a fix, ensuring the visibility of the complete transaction history.<br /><br />We appreciate your patience and understanding during this resolution process. If you encounter any further issues or have additional questions, please don't hesitate to reach out to our support team.</p><p><small>Jan <var data-var='date'>16</var>, <var data-var='time'>14:04</var> AEDT</small><br><strong>Update</strong> - We wanted to keep you informed about the ongoing resolution efforts for the reported issue.<br /><br />According to the latest update from the Data Holders, a fix was implemented yesterday showing now transaction data for transactions posted from 15 January 2024. However, transaction data spanning between 31 December 2023 and 15 January 2024 is still not visible.<br /><br />Please be assured that the Data Holders are actively working with urgency to expedite the availability of this missing data. Your satisfaction is our priority, and we sincerely apologize for any inconvenience this may have caused.<br /><br />We appreciate your continued patience and understanding as we work towards a swift resolution. If you have any further questions or concerns, please don't hesitate to contact our support team.</p><p><small>Jan <var data-var='date'>15</var>, <var data-var='time'>17:48</var> AEDT</small><br><strong>Identified</strong> - Several data holders are experiencing issues in fetching new transactions post-31 December 2023. <br /><br />The affected data holders are below: <br /><br />AU02801 BCU<br />AU04101 Coastline<br />AU05001 Credit Union<br />AU06401 Gateway Bank<br />AU10701 Qudos<br />AU10801 QCCU<br />AU12401 Summerland<br />AU20010 u Bank<br />AU20120 BHCCU<br />AU20260 Fire Service Credit Union<br />AU20550 South West Slopes Credit Union Ltd<br />AU08801 Bank Australia<br />AU04501 Beyond Bank<br />AU09901 P&N<br />AU05201 Defence Bank<br /><br />This problem is impacting CDR connections only. <br /><br />We have received confirmation from the data holders that they are diligently working on a solution and anticipate resolving the issue. We understand the importance of timely data access and are optimistic about a swift resolution. Rest assured, we are committed to keeping you updated on the progress. During this period, users may face difficulties in accessing new data from these institutions. <br /><br />For further inquiries or to express any concerns, please reach out to us at support@basiq.io. <br /><br />We appreciate your patience and understanding in this matter.</p>tag:status.basiq.io,2005:Incident/190507872023-11-14T09:26:45+11:002023-11-14T09:26:46+11:00Scheduled Maintenance for ANZ and Planned Upgrade for CBA<p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>09:26</var> AEDT</small><br><strong>Resolved</strong> - Thanks for your patience, this incident has been resolved.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>11:06</var> AEDT</small><br><strong>Update</strong> - Basiq platform and systems are unaffected by the national outage Optus is currently experiencing.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>09:44</var> AEDT</small><br><strong>Identified</strong> - AU00601 - ANZ<br /><br />2023-11-08T21:00:00+10:00 PT4H ANZ systems are scheduled for maintenance, which will commence on 2023-11-08 at 21:00:00 AEST and is expected to conclude around 2023-11-09 at 01:00:00 AEST. <br /><br />Please note that during this maintenance window, access to certain Open Banking Services will be temporarily unavailable.<br /><br />AU04301 - CBA:<br /><br />2023-11-13T07:30:00Z PT1H Hello ADRs, we will be implementing a planned upgrade from 6:30 PM AEST on Monday, November 13th, to 7:30 PM AEST on the same day. <br /><br />During this period, some customers may experience an impact on CDR data sharing services, and the Get Outages API will also undergo updates. <br /><br />We appreciate your patience and understanding during this time. <br /><br />Thank you for choosing CBA Open Banking.</p>tag:status.basiq.io,2005:Incident/185626962023-09-22T09:45:37+10:002023-09-22T09:45:37+10:00CBA OTP Authentication Outage<p><small>Sep <var data-var='date'>22</var>, <var data-var='time'>09:45</var> AEST</small><br><strong>Resolved</strong> - This issue was resolved at 3:30 pm yesterday and we have tested this thoroughly from our side.<br /><br />Don't hesitate to contact support@basiq.io if there are any issues.</p><p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>15:31</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented by CBA and we have tested this from our side. We are now monitoring the connector. <br /><br />Please contact support@basiq.io if you are still having issues.</p><p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>15:21</var> AEST</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>15:20</var> AEST</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>15:20</var> AEST</small><br><strong>Identified</strong> - CBA's OTP Authentication process is in outage currently. This means that the CBA authentication flow cannot be completed and thus new connections are unable to be created. <br /><br />Scope: This is only affecting new Open Banking and Web Connections. Refreshes are still working <br /><br />This has been raised to CBA directly and they are deploying a fix now.</p>tag:status.basiq.io,2005:Incident/182414172023-08-24T23:31:01+10:002023-08-24T23:31:01+10:00Issue with MFA login to the Basiq dashboard<p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>23:31</var> AEST</small><br><strong>Resolved</strong> - Thanks for your patience: this issue has been resolved.<br /><br />If you contacted Basiq support to disable MFA on your login today, you may re-enable it now.<br /><br />As always, please reach out to us at support@basiq.io with any questions or problems.</p><p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>14:45</var> AEST</small><br><strong>Identified</strong> - There is an issue with the MFA feature for the Basiq dashboard. Customers with MFA enabled are receiving a 404 / not found error when trying to login.<br /><br />We are aware of the issue and working on a fix.<br /><br />In the meantime, if you are getting this error and need to login, please reach out directly to us at support@basiq.io and we can assist.</p>tag:status.basiq.io,2005:Incident/173718952023-08-14T16:31:23+10:002023-08-14T16:31:23+10:00AU06701 - Greater Bank - All jobs failing on login step for web connector<p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>16:31</var> AEST</small><br><strong>Resolved</strong> - We have updated our Greater Bank connector and can confirm that it is now working as expected. <br /><br />Thanks for your patience. <br /><br />As always, please reach out to us if you are having any issues.</p><p><small>Jul <var data-var='date'>17</var>, <var data-var='time'>09:28</var> AEST</small><br><strong>Update</strong> - There has been a delay in Greater Bank's activation as a CDR data holder.<br /><br />We do not know the reason or the new date, but as soon as the bank is active we will enable a CDR connector for them and will update this notice.<br /><br />The ACCC's rectification schedule for data holders not yet active is here: https://www.cdr.gov.au/for-providers/rectification-schedules/rectification-schedule-data-holders-not-active</p><p><small>Jun <var data-var='date'>19</var>, <var data-var='time'>12:00</var> AEST</small><br><strong>Update</strong> - Unfortunately we have no option but to decommission the Greater Bank (AU06701) we connector: the bank is under no obligation to support screen scraping and has made a decision to block Basiq and other aggregators of financial data.<br /><br />The bank is obliged to support customers' data sharing via the Consumer Data Right (CDR, or "open banking"); however they are not active yet. They are scheduled to be activated on 30 June 2023 - about 2 weeks' time. <br /><br />Basiq is unable to support Greater Bank customers until the bank is activated as a CDR data holder. We recommend that consumers who have lost services and are inconvenienced as a result of this issue contact the bank's customer service directly.<br /><br />Next actions:<br /><br />( 1 ) Basiq will decommission the Greater Bank web connector<br /><br />( 2 ) The bank is currently scheduled to become active as a CDR data holder by Friday 30 June<br /><br />( 3 ) Once the bank is activated for CDR, Basiq will enable a CDR connector under the same institution ID, AU06701<br /><br />( 4 ) Basiq customers enabled for CDR will be able to offer Greater Bank to their users again<br /><br />We will keep this status notice open until the bank is available for CDR services.<br /><br />CDR rectification schedule for data holders not active: https://www.cdr.gov.au/for-providers/rectification-schedules/rectification-schedule-data-holders-not-active (Greater Bank scheduled for 30 June 2023)</p><p><small>May <var data-var='date'>29</var>, <var data-var='time'>12:28</var> AEST</small><br><strong>Identified</strong> - Greater Bank have made a change to their internet banking portal which effectively detects and blocks the web connections used by Basiq and other aggregators to fetch data from the bank.<br /><br />Banks have no obligation to allow web connections ("screen scraping") - but for most banks if they don't allow web connections there is a strong alternative. The Australian government has mandated that authorised deposit-taking institutions (ADIs) must participate in the new open banking framework known as the Consumer Data Right (CDR). Basiq customers can generally choose whether to fetch data from a given bank via web connections or CDR; over time it is likely that support for web connections may be phased out.<br /><br />However, Greater Bank is not an active participant in the CDR framework. As the bank has started to block web connections, Greater Bank customers are left without an option to programmatically share their banking data with financial services of their choosing.<br /><br />Greater Bank have a page advising customers on their current CDR status, here: https://www.greater.com.au/openbanking<br /><br />We recommend that Greater Bank customers inconvenienced by this action reach out to the bank directly to understand their options and timeline for sharing data with accredited recipients.<br /><br />We will update you via this ticket on a timeline to deactivating the Greater Bank web connector.</p><p><small>May <var data-var='date'>26</var>, <var data-var='time'>10:53</var> AEST</small><br><strong>Investigating</strong> - All Greater Bank jobs are currently failing on the login step.<br /><br />Our team are investigating and we will update this notice with progress.</p>tag:status.basiq.io,2005:Incident/180808822023-08-08T12:52:40+10:002023-08-08T12:52:40+10:00Consent UI Issue<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>12:52</var> AEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>12:51</var> AEST</small><br><strong>Monitoring</strong> - We are pleased to announce that the issue with our Consent UI has been successfully resolved. Our engineering team has implemented a fix, and we have conducted thorough testing to ensure that the Consent UI is now functioning as intended.<br /><br />If you encounter any further issues or have any questions, please don't hesitate to contact our support team at support@basiq.io. We will continue to keep you updated on any developments and strive to provide you with the best service possible.</p><p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>12:43</var> AEST</small><br><strong>Update</strong> - Updates:<br /><br />Our engineering team is fully engaged and currently applying the fix. We recognise the importance of user consent and data privacy. We apologize for any inconvenience this issue may have caused and assure you that we are doing everything in our power to resolve it as quickly as possible. We will continue to provide updates on this status page as we make progress towards resolving the issue. Thank you for your patience and understanding.</p><p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>12:22</var> AEST</small><br><strong>Identified</strong> - We have identified an issue with our Consent UI that is currently affecting user experience and data connections only for new users. Our team is actively investigating the root cause and working towards a resolution.</p>tag:status.basiq.io,2005:Incident/180161622023-08-01T12:34:41+10:002023-08-01T12:34:41+10:00ME Go (AU20850) - New connector available via CDR<p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>12:34</var> AEST</small><br><strong>Resolved</strong> - ME Bank have launched a new brand called ME Go, to service customers of their digital-only app. <br /><br />ME Bank have set up a separate brand for ME Go under the CDR framework, which requires a new connector in Basiq to service these customers.<br /><br />The new connector has been assigned a Basiq institution ID of AU20850 and is visible in your Basiq dashboard > Status page, and in the /connectors endpoint of the API.<br /><br />The new connector has been released in beta, but not enabled by default. <br /><br />If you would like to be an early adopter of the ME Go connector, please reach out to us at support@basiq.io and we will enable you.</p>tag:status.basiq.io,2005:Incident/179730352023-07-28T10:07:51+10:002023-07-28T10:07:51+10:00Scheduled maintenance - Macquarie - Open banking authentication flow update - 6pm AEST Thurs 27 July 2023<p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>10:07</var> AEST</small><br><strong>Resolved</strong> - Work completed as scheduled overnight, no issues noted.</p><p><small>Jul <var data-var='date'>27</var>, <var data-var='time'>17:13</var> AEST</small><br><strong>Identified</strong> - Further to the authentication flow updates started earlier in the month (here: https://status.basiq.io/incidents/8g3dz20zstr8)<br /><br />We will enable the new authentication flow for Macquarie (AU00301) tonight at 6pm AEST.<br /><br />These changes relate to CDR only.<br /><br />No impact anticipated.</p>tag:status.basiq.io,2005:Incident/178414862023-07-14T09:18:15+10:002023-07-17T09:18:30+10:00Scheduled maintenance - CBA and others - Open banking authentication flow update - 5pm AEST Thurs 13 July 2023<p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>09:18</var> AEST</small><br><strong>Resolved</strong> - Work completed with no impact as expected.</p><p><small>Jul <var data-var='date'>13</var>, <var data-var='time'>16:57</var> AEST</small><br><strong>Identified</strong> - Further to the authentication flow updates started last week (here: https://status.basiq.io/incidents/8g3dz20zstr8)<br /><br />We are ready to add support for the new authentication code flow for the following data holders:<br /><br />AU04301 - CBA<br />AU00401 - BankWest<br />AU20150 - CommBiz<br />AU07601 - IMB<br /><br />These changes relate to CDR only.<br /><br />Work planned to start at 5pm AEST; no impact anticipated.</p>tag:status.basiq.io,2005:Incident/178198752023-07-12T09:58:28+10:002023-07-12T09:58:28+10:00Scheduled maintenance - ING and Heritage - Open banking authentication flow update - 5pm AEST Thurs 6 July 2023<p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>09:58</var> AEST</small><br><strong>Resolved</strong> - Work has completed, no issues noted.</p><p><small>Jul <var data-var='date'>11</var>, <var data-var='time'>12:52</var> AEST</small><br><strong>Identified</strong> - Further to the authentication flow updates started last week (here: https://status.basiq.io/incidents/8g3dz20zstr8)<br /><br />We will upgrading support for outstanding data holders who were unable to be upgraded last week. This work will be rolled out per data holder as issues preventing the upgrade for each are resolved.<br /><br />Tonight (Tues 11 July) we will be adding support for the new authentication flows for ING (AU00201) and Heritage (AU06801).<br /><br />These changes relate to CDR only.<br /><br />Work planned to start at 5pm AEST; no impact anticipated.</p>tag:status.basiq.io,2005:Incident/177783352023-07-07T13:02:26+10:002023-07-07T13:02:26+10:00Scheduled maintenance - Open banking authentication flow update - 8pm AEST Thurs 6 July 2023<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>13:02</var> AEST</small><br><strong>Resolved</strong> - We have rolled back the change for the following four data holders:<br /><br />AU15401 (Woolworths)<br />AU15801 (Myer One)<br />AU20020 (Aussie Home Loans)<br />AU20110 (Bell Potter)<br /><br />We were not able to update our registration to the new authentication flow for these four banks. We will work with them to resolve those issues, and will switch them over together with the other outstanding data holders previously noted.<br /><br />No other issues noted. We will close this notice now.<br /><br />As always, please reach out to support@basiq.io with any questions or problems.</p><p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>01:34</var> AEST</small><br><strong>Monitoring</strong> - Work has completed, we are monitoring for stability.</p><p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>20:41</var> AEST</small><br><strong>Update</strong> - Initial setup and testing is complete. We are starting the work in production now.</p><p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>18:02</var> AEST</small><br><strong>Identified</strong> - We will be deploying a change tonight to the way that we authenticate with data holders (banks) via CDR.<br /><br />This change should be transparent to our partners and no impact is anticipated, however this notice is here for your visibility.<br /><br />We are not anticipating any impact to service. If anything does go wrong, it will be in the redirect from Basiq to the bank and / or from the bank back to Basiq. We will be monitoring service for all data holders and will update this status notice.<br /><br />92 data holders will be updated tonight; these data holders have all completed testing successfully. The remaining data holders will be switched to the new authentication flow in coming weeks as outstanding issues with them are confirmed resolved.<br /><br />The full list of data holders to be switched tonight is below:<br /><br />AU00101 (Bendigo)<br />AU00601 (ANZ)<br />AU00701 (BOQ)<br />AU00901 (Great Southern Bank)<br />AU01001 (NAB)<br />AU02501 (AMB)<br />AU02801 (BCU)<br />AU03101 (Bank of Sydney)<br />AU03201 (BankSA)<br />AU04101 (Coastline)<br />AU04501 (Beyond Bank)<br />AU05001 (Credit Union)<br />AU05201 (Defence Bank)<br />AU06201 (First Option)<br />AU06401 (Gateway Bank)<br />AU07201 (HSBC)<br />AU07301 (Hume Bank)<br />AU08801 (Bank Australia)<br />AU08901 (ME Bank)<br />AU09201 (MyState)<br />AU09301 (NPBS)<br />AU09701 (Orange CU)<br />AU09801 (People's Choice)<br />AU09901 (P&N)<br />AU10501 (RACQ)<br />AU10701 (Qudos)<br />AU10801 (QCCU)<br />AU11301 (RAMS)<br />AU11901 (G&C Mutual)<br />AU12301 (St. George)<br />AU12401 (Summerland)<br />AU13601 (UBank)<br />AU14201 (Westpac)<br />AU15401 (Woolworths)<br />AU15501 (Qantas)<br />AU15801 (Myer One)<br />AU16001 (Virgin Money)<br />AU16501 (Bank Vic)<br />AU18001 (Bank First)<br />AU18901 (RaboDirect Online Savings)<br />AU20010 (u Bank)<br />AU20020 (Aussie Home Loans)<br />AU20030 (Australian Mutual Bank LTD)<br />AU20040 (Australian Unity Bank)<br />AU20050 (Auswide Bank Ltd)<br />AU20070 (Bank of China)<br />AU20080 (Bank of us)<br />AU20110 (Bell Potter)<br />AU20120 (BHCCU)<br />AU20130 (BOQ Specialist)<br />AU20140 (Card Services)<br />AU20160 (Central Murray Credit Union Limited)<br />AU20170 (Central West CUL)<br />AU20220 (DDH Graham)<br />AU20230 (Dnister)<br />AU20250 (Family First)<br />AU20260 (Fire Service Credit Union)<br />AU20270 (Firefighters Mutual Bank)<br />AU20280 (First Choice Credit Union)<br />AU20290 (Geelong Bank)<br />AU20300 (gmcu)<br />AU20310 (Health Professionals Bank)<br />AU20320 (Hiver Bank)<br />AU20330 (Horizon Bank)<br />AU20350 (Illawarra Credit Union Limited)<br />AU20370 (Judo Bank)<br />AU20380 (Kogan Money Credit Cards)<br />AU20390 (Laboratories Credit Union)<br />AU20410 (Maitland Mutual Limited)<br />AU20460 (Police Credit Union Ltd)<br />AU20480 (QBANK)<br />AU20510 (Regional Australia Bank)<br />AU20520 (Reliance Bank)<br />AU20530 (RSL Money)<br />AU20550 (South West Slopes Credit Union Ltd)<br />AU20560 (Southern Cross Credit Union)<br />AU20580 (The Capricornian)<br />AU20590 (The Mac)<br />AU20600 (TMCU)<br />AU20610 (Tyro Payments)<br />AU20620 (UniBank)<br />AU20630 (Unity Bank)<br />AU20650 (WAW)<br />AU20670 (Woolworths Team Bank)<br />AU20680 (Up Bank)<br />AU20690 (Thriday)<br />AU20720 (Cairns bank)<br />AU20740 (Warwick)<br />AU20750 (ANZ Plus)<br />AU20760 (Unloan)<br />AU20770 (Challenger)<br />AU20780 (SocietyOne)<br /><br /><br />The following institutions have **not yet** passed testing and will be done at a later date:<br /><br />AU00201 (ING Direct)<br />AU00301 (Macquarie)<br />AU00401 (Bankwest)<br />AU00501 (AMP)<br />AU00801 (Citibank)<br />AU01101 (Suncorp)<br />AU03001 (BOM)<br />AU04301 (CBA)<br />AU06801 (Heritage Bank)<br />AU07601 (IMB)<br />AU12701 (TMBank)<br />AU15301 (Coles)<br />AU17001 (Paypal)<br />AU20150 (CBA - CommBiz)<br />AU20800 (Amigo)<br />AU20810 (HSBC Wholesale Banking)<br />AU20820 (Wise)</p>tag:status.basiq.io,2005:Incident/177671332023-07-06T10:35:08+10:002023-07-06T10:35:08+10:00AU07201 - HSBC - Data holder portal unavailable for new connections<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>10:35</var> AEST</small><br><strong>Resolved</strong> - Issue has been resolved: HSBC is working OK for new CDR connections.<br /><br />As always, please report any questions or problems to us at support@basiq.io</p><p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>15:01</var> AEST</small><br><strong>Identified</strong> - Some consumers selecting HSBC in the Basiq consent UI may receive an error, "Syntax error: Unexpected token 'I', "Internal s"... is not valid JSON".<br /><br />This is due to changes in the authentication flow between data holders (in this case, HSBC) and data recipients, such as Basiq and our affiliates and representatives. Work was already in flight to add support for the new flow across all data holders; as HSBC has switched earlier than anticipated we will prioritise them and will switch as soon as possible. Unfortunately this may take several days as the changes are complex.<br /><br />Only new connections are affected: existing connections are refreshing data without issue.<br /><br />We recommend that our partners disable HSBC / AU07201 in their consent UIs until this incident is resolved.<br /><br />Note that the HSBC connector status in your Basiq dashboard is operational: this is because refresh jobs (which form the bulk of data requests to the bank) are working OK.<br /><br />We will update this ticket was soon as possible, for you to re-enable HSBC in the UI.</p>tag:status.basiq.io,2005:Incident/177042472023-06-28T22:08:19+10:002023-06-28T23:05:08+10:00Scheduled maintenance for Basiq payments - 21:00 AEST Weds 28 June 2023<p><small>Jun <var data-var='date'>28</var>, <var data-var='time'>22:08</var> AEST</small><br><strong>Resolved</strong> - Scheduled maintenance completed.<br /><br />There was brief interruption to the following services during the work:<br /><br />* Consent UI<br />* GET /users/{userId}/payments/accounts<br />* GET /payments/payouts/<br />* GET /payments/payouts/{id}<br />* GET /payments/payrequests<br />* GET /payments/payrequests/{id}<br /><br />Apologies to our partners and their customers for any inconvenience; we hope that advance notice of the planned maintenance assisted with any support calls that may have come in.<br /><br />As always, please reach out to us at support@basiq.io with any questions or problems.</p><p><small>Jun <var data-var='date'>28</var>, <var data-var='time'>21:09</var> AEST</small><br><strong>Update</strong> - We have started the work.<br /><br />Anticipating no interruption to service however we will keep you updated via this notice.</p><p><small>Jun <var data-var='date'>28</var>, <var data-var='time'>10:45</var> AEST</small><br><strong>Identified</strong> - We will be upgrading our payments infrastructure this evening from 21:00 AEST - 23:00 AEST (11:00 - 13:00 UTC).<br /><br />We are not anticipating any interruption to service.<br /><br />For your visibility, we will keep this status notice updated with progress.<br /><br />As always, if you have any questions or concerns please reach out to support@basiq.io any time.</p>tag:status.basiq.io,2005:Incident/176836202023-06-26T15:12:56+10:002023-06-26T15:12:57+10:00CBA Platform Experiences Widespread Outage Impacting Data Retrieval<p><small>Jun <var data-var='date'>26</var>, <var data-var='time'>15:12</var> AEST</small><br><strong>Resolved</strong> - The issue has been effectively addressed by CBA. We have thoroughly tested and verified that everything is now functioning properly.<br /><br />To ensure your continued satisfaction, our team will closely monitor the situation for the remainder of the day. If you encounter any further difficulties or have any additional concerns, please don't hesitate to reach out to our support team at support@basiq.io.<br /><br />Thank you for your patience and understanding.</p><p><small>Jun <var data-var='date'>26</var>, <var data-var='time'>12:37</var> AEST</small><br><strong>Identified</strong> - The CBA platform is currently undergoing a widespread outage, which is resulting in complications for Data Recipients such as Basiq in retrieving CDR and Web connector data from CBA. <br /><br />This is due to multiple services being affected by the outage, as stated on CBA's incident page available at: https://www.commbank.com.au/about-us/support/commbank-incidents.html. <br /><br />We sincerely apologize for any inconvenience caused and assure you that we are actively working to resolve the issue as quickly as possible.</p>tag:status.basiq.io,2005:Incident/175890062023-06-20T10:09:31+10:002023-06-20T10:09:31+10:00AU08801 - Bank Australia - Web jobs failing with invalid credentials errors<p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>10:09</var> AEST</small><br><strong>Resolved</strong> - Closing this notice as this issue has been resolved.<br /><br />As always, please reach out to support@basiq.io with any questions or concerns, any time.</p><p><small>Jun <var data-var='date'>19</var>, <var data-var='time'>23:19</var> AEST</small><br><strong>Update</strong> - We have run a script to re-activate affected connections.<br /><br />No issues noted. <br /><br />We will keep this notice open for monitoring until the morning.</p><p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>00:50</var> AEST</small><br><strong>Monitoring</strong> - Confirming that the bank made a change to their internet banking login process. A selector which previously indicated that the user's credentials are invalid is now present on every login.<br /><br />We have updated our Bank Australia web connector, this issue should be resolved going forward.<br /><br />Affected connections from the past week will have an invalid status. There are two options to reactivate these connections:<br /><br />( 1 ) You can prompt your users with an update connection request, as you normally do if their credentials are actually invalid<br /><br />( 2 ) We will run a script to patch the status of affected connections<br /><br />The patch for ( 2 ) will likely be ready on Monday overnight. If you can’t wait, we recommend going with option ( 1 ).</p><p><small>Jun <var data-var='date'>16</var>, <var data-var='time'>12:54</var> AEST</small><br><strong>Investigating</strong> - Web connections for Bank Australia are currently failing with invalid credentials errors. Typically this would indicate that the user has not provided correct login credentials for the institutions, but in this case there appears to have been a change to the bank's internet banking login process which is affecting all customers.<br /><br />CDR connections are not affected by this issue and remain fully functional. We recommend that any customers who are enabled for CDR switch the aggregation method for Bank Australia (AU08801) switch over to CDR. You can do this in your Basiq dashboard > (select application) > Customise UI > Institutions > Bank Australia > (select CDR).<br /><br />Our tech team are investigating the nature of the internet banking issue and we will update this status notice with advice.<br /><br />As always, please reach out to support@basiq.io if you need any help or advice.</p>tag:status.basiq.io,2005:Incident/172243312023-05-12T14:55:46+10:002023-05-12T14:56:17+10:00CBA OpenBanking Redirect Failing<p><small>May <var data-var='date'>12</var>, <var data-var='time'>14:55</var> AEST</small><br><strong>Resolved</strong> - This incident has now been resolved by the CBA. We are still monitoring it closely. Thanks for your Patience.</p><p><small>May <var data-var='date'>12</var>, <var data-var='time'>11:54</var> AEST</small><br><strong>Identified</strong> - We are currently experiencing difficulties in successfully redirecting CBA Data Holder portal for Open Banking.<br /><br />We are encountering a 404 error, indicating that the requested page is not found.<br /><br />This issue is impacting multiple different Aggregators/ADRs like Basiq and is affecting all CBA OpenBanking consumers<br /><br />We have raised this concern with CBA directly via CDR portal. We will keep you posted with the further updates here.</p>tag:status.basiq.io,2005:Incident/169764222023-04-28T10:41:40+10:002023-04-28T10:41:40+10:00[ANZ] - (AU00601) Open Banking Connector in Major Outage<p><small>Apr <var data-var='date'>28</var>, <var data-var='time'>10:41</var> AEST</small><br><strong>Resolved</strong> - ANZ has remained stable since they applied the fix - closing this notice now.<br /><br />As always, please reach out to support@basiq.io with any questions or problems.</p><p><small>Apr <var data-var='date'>27</var>, <var data-var='time'>13:28</var> AEST</small><br><strong>Monitoring</strong> - ANZ have addressed the issue, we have tested and confirmed OK.<br /><br />We will keep this ticket open and continue to monitor for the rest of the day. If you have any further trouble, please reach out to support@basiq.io.</p><p><small>Apr <var data-var='date'>27</var>, <var data-var='time'>09:35</var> AEST</small><br><strong>Identified</strong> - ANZ's platform is currently experiencing issues on their Open Banking platform. This is causing downstream issues for Data Recipients like Basiq to fetch CDR data from ANZ's APIs. <br /><br />Rest assured, our team has swiftly escalated the matter to ANZ and they are conducting a thorough investigation to identify the root cause of the problem. <br /><br />We apologise for any inconvenience caused and are working diligently to resolve the issue as soon as possible.</p>tag:status.basiq.io,2005:Incident/163213632023-03-16T16:04:27+11:002023-03-16T16:04:32+11:00[ING] - (AU00201) Open Banking Jobs failing on the Transactions Fetch<p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>16:04</var> AEDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>14:19</var> AEDT</small><br><strong>Monitoring</strong> - ING has implemented a fix for this specific issue over the weekend and as a result, we are currently seeing a strong success rate.<br /><br />Basiq will continue to closely monitor this issue in collaboration with ING to ensure that there are no further disruptions.<br /><br />Thank you for your patience and understanding during this time.</p><p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>18:04</var> AEDT</small><br><strong>Identified</strong> - Basiq is currently facing difficulties retrieving data from the Data Holder's Open Banking accounts API endpoints through ING's platform.<br /><br />Our team has promptly escalated the matter to ING, and they are currently conducting a thorough investigation to identify the root cause of the problem</p>tag:status.basiq.io,2005:Incident/162442572023-03-02T18:00:32+11:002023-03-02T18:00:32+11:00[ING] - (AU00201) Open Banking Jobs failing on the Accounts Ep<p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>18:00</var> AEDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>16:56</var> AEDT</small><br><strong>Monitoring</strong> - Issue with the accounts fetch for ING has mostly resolved. <br /><br />However, we are closely monitoring the situation to ensure that there are no further disruptions. <br /><br />We are continuing to work with ING to investigate the root cause of the problem and prevent it from occurring in the future. We appreciate your patience and understanding, and we will provide additional updates as soon as possible. Thank you.</p><p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>16:29</var> AEDT</small><br><strong>Identified</strong> - Basiq is currently facing difficulties retrieving data from the Data Holder's Open Banking accounts API endpoints through ING's platform.<br /><br />Our team has promptly escalated the matter to ING, and they are currently conducting a thorough investigation to identify the root cause of the problem.</p>tag:status.basiq.io,2005:Incident/162857052023-03-01T10:08:34+11:002023-03-01T10:08:36+11:00[PCCU] Push Authorisation Request failing<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>10:08</var> AEDT</small><br><strong>Resolved</strong> - A fix has been implemented and this has resolved the issue. <br /><br />Thank you all for your patience. <br /><br />Any queries? Please reach out to support@basiq.io</p><p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>13:28</var> AEDT</small><br><strong>Investigating</strong> - Basiq is currently facing PAR request failures with PCCU Data Holder. <br /><br />We are continuing to work with PCCU to investigate the root cause of the problem and prevent it from occurring in the future. We appreciate your patience and understanding, and we will provide additional updates as soon as possible. Thank you.</p>tag:status.basiq.io,2005:Incident/163213552023-03-01T00:00:00+11:002023-03-02T18:02:51+11:00[ING] - (AU00201) Open Banking Jobs failing on the Transactions Ep<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>00:00</var> AEDT</small><br><strong>Resolved</strong> - Basiq is currently facing difficulties retrieving data from the Data Holder's Open Banking accounts API endpoints through ING's platform.<br /><br /><br />Our team has promptly escalated the matter to ING, and they are currently conducting a thorough investigation to identify the root cause of the problem.</p>tag:status.basiq.io,2005:Incident/162441502023-02-27T15:58:04+11:002023-02-27T15:58:04+11:00[PCCU] - (AU09801) Open Banking Jobs Failing on Transactions Fetch<p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>15:58</var> AEDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>17:08</var> AEDT</small><br><strong>Monitoring</strong> - PCCU has identified the root cause of the issue and released a tactical fix to address it last night.<br /><br />We will continue to monitor the situation closely to ensure that there are no further disruptions.</p><p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>16:18</var> AEDT</small><br><strong>Identified</strong> - ADR providers such as Basiq are encountering challenges in retrieving transactions from the Data Holder's Open Banking transactions API endpoints. <br /><br />Our team has proactively escalated this issue to PCCU, and they are presently conducting an investigation into the matter.</p>tag:status.basiq.io,2005:Incident/162008912023-02-22T15:32:44+11:002023-02-22T15:32:45+11:00ING - Switching Data holder Solution<p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>15:32</var> AEDT</small><br><strong>Resolved</strong> - This incident has been resolved. <br /><br />Please reach out to support@basiq.io if you have any questions or concerns.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>08:26</var> AEDT</small><br><strong>Monitoring</strong> - Thank you all for your patience. <br /><br />We have successfully connected to the new ING data holder overnight. <br /><br />The new ING platform seems to be functioning well with upgrades to full features such as Joint accounts and a working consent dashboard. <br /><br />Would you please turn the ING OB connector back on in your BASIQ Dashboard and confirm the same. <br /><br />Any queries? Please reach out to support@basiq.io</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>13:05</var> AEDT</small><br><strong>Identified</strong> - For Basiq customers using Open Banking, please note that ING will be switching data holder solutions on the 21st of Feb 2023.<br /><br />As such, we recommend you disable the ING Open Banking connector in your dashboard from today (20th Feb) turn it back on on the 22nd Feb. <br /><br />We will keep you posted here with the further updates. <br /><br />Any queries? Please reach out to support@basiq.io</p>tag:status.basiq.io,2005:Incident/160863242023-02-20T13:03:39+11:002023-02-20T13:03:41+11:00Some institutions failing redirect to data holder for CDR user onboarding<p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>13:03</var> AEDT</small><br><strong>Resolved</strong> - This incident has been resolved. <br /><br />The DH advised that there was an issue with processing the certificates while handshake connection between BASIQ and DH and this has now been fixed from their end. <br /><br />For any further queries, please reach out to support@basiq.io.</p><p><small>Feb <var data-var='date'>13</var>, <var data-var='time'>11:55</var> AEDT</small><br><strong>Monitoring</strong> - Errors have cleared and all four data holders are now redirecting successfully.<br /><br />We are awaiting update from the data holders regarding root cause and will keep this status notice open while we monitor; but the issue does appear to be resolved by the banks.<br /><br />Last redirection error was 19:30 AEDT on Sunday 12 February.</p><p><small>Feb <var data-var='date'>10</var>, <var data-var='time'>18:50</var> AEDT</small><br><strong>Identified</strong> - We have some smaller data holders failing redirects to their CDR portals.<br /><br />In all cases we are getting timeouts or incomplete responses from the data holders - we have raised tickets with the data holders in the CDR service portal and are awaiting updates; in the meantime users will be unable to connect these institutions below:<br /><br />Qantas Money<br />Kogan Money Credit Cards<br />Coles Financial Services<br />Citi Australia<br /><br />Note this affects CDR connections only.<br /><br />Please any concerns or questions through to us at support@basiq.io</p>tag:status.basiq.io,2005:Incident/160390992023-02-06T21:03:23+11:002023-02-06T21:03:24+11:00Some Web Jobs are failings for ANZ & CBA<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>21:03</var> AEDT</small><br><strong>Resolved</strong> - Issue has been resolved<br /><br />Apologies to our partners and their end users for the inconvenience caused, and thank you for your patience while we investigated.<br /><br />As always, please reach out with any questions and concerns to support@basiq.io.</p><p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>20:57</var> AEDT</small><br><strong>Identified</strong> - The issue has been identified and a fix is been implemented. <br /><br />We are working on the issue and will update you via this status notice.</p><p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>20:16</var> AEDT</small><br><strong>Investigating</strong> - Our team have identified an issue that some high and medium priority jobs for web connections are failing. Our team is currently investigating this issue. <br /><br />We are working on the issue and will update you via this status notice.</p>