Jun <var data-var='date'>22</var>, <var data-var='time'>19:25</var> BST Resolved - The incident has now been resolved, as ongoing monitoring has shown the platform has returned to normal stability. If you are still affected by this issue, please contact support@codat.io Jun <var data-var='date'>22</var>, <var data-var='time'>16:43</var> BST Monitoring - We have implemented a fix. Affected users should notice that API queries have returned to normal, and they can now login to the Portal. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues, please contact support@codat.io for further assistance. Jun <var data-var='date'>22</var>, <var data-var='time'>16:22</var> BST Investigating - Our monitoring has flagged a higher than usual volume of errors. Affected users may notice that API calls are erroring, and they may be unable to login to the Codat Portal. This could have been noticed between 15:03UTC - 15:30UTC This incident will be updated as soon as we have identified the issue.

Intermittent API errors

Jun <var data-var='date'> 2</var>, <var data-var='time'>15:45</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to create companies with tags as normal. If you are still affected by this issue, please contact support@codat.io Jun <var data-var='date'> 2</var>, <var data-var='time'>15:07</var> BST Monitoring - We have implemented a fix in production. Affected users should now notice that they're now able to create companies with tags as normal. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Jun <var data-var='date'> 2</var>, <var data-var='time'>15:01</var> BST Identified - We are currently investigating an issue preventing users from creating companies with tags. This incident will be updated as soon as we have successfully tested and rolled out a fix in production.

Users unable to create companies with Tags

May <var data-var='date'>29</var>, <var data-var='time'>15:50</var> BST Resolved - This incident has been resolved. Pushing to QBD is now working as expected. May <var data-var='date'>29</var>, <var data-var='time'>15:07</var> BST Monitoring - We have implemented a fix. Affected users should now notice that their QBD push operations now no longer fail with an error message referencing a Third Party Gateway. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. May <var data-var='date'>29</var>, <var data-var='time'>15:03</var> BST Investigating - We are actively investigating an issue preventing users from push items to QuickBooks Desktop Affected users will notice that their push operations are failing with 'Third-party gateway responded with an erorr status but did not return a valid error body' This incident will be updated as soon as we have identified the issue, and no later than 16:03

QuickBooks Desktop Push Operation Outage

May <var data-var='date'>29</var>, <var data-var='time'>12:17</var> BST Resolved - End-users attempting to link to TrueLayer would've experienced an issue for an approximately 40 min period this morning, where the callbacks to the Codat system, after authenticating on the banking-provider side were failing with an error page which read "Unknown Destination". Affected users would have noticed that after they entered their credentials in their banking-provider's app, when they would ordinarily get directed back to the Codat system, they would've instead seen an "Unknown Destination" error in their browser. We have resolved the incident now. End-users will be able to link to TrueLayer successfully and be directed back to Codat's application.

TrueLayer call backs routing to "Unknown Destination" error page.

May <var data-var='date'>28</var>, <var data-var='time'>16:30</var> BST Resolved - Our monitoring flagged that a higher than normal number of Plaid banking-transaction fetches were failing between 29th May 16:19 GMT and 1st June 16:30 GMT. Affected users would have noticed that for Plaid connected companies, banking-transaction datasets were failing with a FetchError, when it was their first ever attempt to fetch this particular dataset. The cause of the issue has been identified as a DNS change preventing us from receiving webhooks from Plaid's service. The DNS change has now been rectified and we are again able to receive messages from the Plaid system. We have improved our testing around these types of changes to our system. If you are still affected by this issue, please contact support@codat.io for further assistance.

Plaid banking-transaction fetches failing intermittently.

Apr <var data-var='date'>22</var>, <var data-var='time'>13:24</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to successfully complete push operations to QuickBooks Desktop without disruption. If you are still affected by this issue, please contact support@codat.io Apr <var data-var='date'>21</var>, <var data-var='time'>19:51</var> BST Monitoring - We have implemented a fix in Production. Affected users should now notice that all Quickbooks Desktop push operations are completing successfully. Please keep in mind that some Push Operations may remain in a Pending status if the end user's computer is offline. These Pending Push operations will resume when they are back online. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Apr <var data-var='date'>21</var>, <var data-var='time'>18:41</var> BST Identified - The issue has been identified and a fix is being implemented. Apr <var data-var='date'>21</var>, <var data-var='time'>17:02</var> BST Update - We are continuing to investigate this issue. Apr <var data-var='date'>21</var>, <var data-var='time'>16:59</var> BST Investigating - We are actively investigating an issue preventing QuickBooks Desktop Push Operations from completing as quickly as expected. Affected users will notice that a small subset of their QuickBooks Desktop push Operations may take a lot longer than usual to complete, and will appear as though stuck in pending for a long time. This incident will be updated as soon as we have identified the issue, and no later than 18:00

QuickBooks Desktop Push Operations not moving beyond Pending

Mar <var data-var='date'>26</var>, <var data-var='time'>15:23</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to sync datasets without disruption. If you are still affected by this issue, please contact support@codat.io Mar <var data-var='date'>26</var>, <var data-var='time'>11:21</var> GMT Monitoring - We have implemented a fix in production. Affected users should now notice that datasets are processing normally. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Mar <var data-var='date'>26</var>, <var data-var='time'>10:47</var> GMT Investigating - We are actively investigating an issue causing a delay in datasets moving from the processing stage. This incident will be updated as soon as we have identified the issue.

Dataset delay in processing stage

Mar <var data-var='date'>19</var>, <var data-var='time'>13:22</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to create Bank Accounts on behalf of Xero connected companies. If you are still affected by this issue, please contact support@codat.io Mar <var data-var='date'>19</var>, <var data-var='time'>13:09</var> GMT Monitoring - We have implemented a fix. Affected users should now notice that they are again able to push Bank Accounts on behalf of Xero connected companies. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Mar <var data-var='date'>19</var>, <var data-var='time'>12:49</var> GMT Investigating - We are actively investigating an issue preventing users from Creating Bank Accounts through Codat's API for Xero connected companies. Affected users may notice that their Bank Account Push Operations Fail with a 524 error. This incident will be updated as soon as we have identified the issue, and no later than 13:48

Push Bank Accounts Intermittently Failing for Xero Connections

Mar <var data-var='date'>13</var>, <var data-var='time'>13:30</var> GMT Resolved - Our monitoring flagged that datasets were failing with an InternalError between 13.20 GMT and 13.25 GMT when a fix was released. This resolved the issue for the majority however some integrations would have still seen this until 13.35 GMT. The cause of the issue has been identified as an issue with a release causing failures. Service has now been restored. If you are still affected by this issue, please contact support@codat.io for further assistance.

Datasets failing with InternalErrors

Mar <var data-var='date'>11</var>, <var data-var='time'>12:00</var> GMT Resolved - During this incident, a small subset of our users may have noticed that they were unable to connect their Oracle NetSuite instances to Codat. After having given permission in the NetSuite system, upon being redirected back to Codat they would've immediately been shown a screen stating "There has been an error connecting to Oracle NetSuite". This was as a result of a backend configuration change, which has subsequently been reverted. End Users will now be able to connect their Oracle NetSuite instances to Codat as expected.

Oracle NetSuite intermittent linking errors

Mar <var data-var='date'> 6</var>, <var data-var='time'>14:53</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to push attachments to QBO Sandbox without disruption. If you are still affected by this issue, please contact support@codat.io Mar <var data-var='date'> 6</var>, <var data-var='time'>10:38</var> GMT Monitoring - We have implemented a fix in production. Affected users should now notice that they're able to push attachments to QBO Sandbox. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Mar <var data-var='date'> 6</var>, <var data-var='time'>10:26</var> GMT Investigating - We are actively investigating an issue preventing users from pushing attachments to Quickbooks Online Sandbox. Affected users will notice that they receive a 400 error response when attempting to push attachments to Quickbooks Online Sandbox. This incident will be updated as soon as we have identified the issue, and no later than 11.30AM GMT.

Unable to push attachments to QBO Sandbox

Feb <var data-var='date'>24</var>, <var data-var='time'>14:59</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to generate Credit Model and Categorized Bank Statements reports in Production without disruption. If you are still affected by this issue, please contact support@codat.io Feb <var data-var='date'>24</var>, <var data-var='time'>11:10</var> GMT Monitoring - We have implemented a fix in Production. Affected users should now notice that Credit Model and Categorized Bank Statements reports complete successfully. If you were affected, please queue the report in the Codat portal or via the API. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Feb <var data-var='date'>24</var>, <var data-var='time'>10:38</var> GMT Update - We are continuing to investigate this issue. Feb <var data-var='date'>24</var>, <var data-var='time'>10:34</var> GMT Investigating - We are actively investigating an issue preventing users from generating reports for the Credit Model and the Categorized Bank Statements. Affected users will notice that the Credit Model Report and the Categorized Bank Statements reports are currently timing out and failing to generate. This incident will be updated as soon as we have identified the issue, and no later than 11:30am UK time.

Credit Model and Categorized Bank Statements reports generation unavailable in Production

Feb <var data-var='date'>24</var>, <var data-var='time'>11:12</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to push transactions to QuickBooks Online without disruption. If you are still affected by this issue, please contact support@codat.io. Feb <var data-var='date'>24</var>, <var data-var='time'>02:30</var> GMT Monitoring - We have implemented a fix in Production. Affected users should now notice that they are able to push data to QBO successfully. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Feb <var data-var='date'>23</var>, <var data-var='time'>23:47</var> GMT Investigating - We are actively investigating an issue where a number of QBO Push Operations are failing with an "invalid_grant" or "Poisoned" response. This incident will be updated as soon as we have identified the issue.

QBO Push Operations may fail

Feb <var data-var='date'>20</var>, <var data-var='time'>09:20</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to retrieve reports via the Codat portal without disruption. If you are still affected by this issue, please contact support@codat.io Feb <var data-var='date'>19</var>, <var data-var='time'>14:17</var> GMT Monitoring - We have implemented a fix in Production. Affected users should now notice that they are able to run the reports successfully in Production. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Feb <var data-var='date'>19</var>, <var data-var='time'>13:25</var> GMT Identified - We are actively investigating an issue preventing users from generating Spend Insight, Categorized Bank Statement reports. Affected users will notice that reports are much slower to complete and upon completion, return a 'Failed' status. This incident will be updated as soon as we have identified the issue, and no later than 15:00 UK time.

Report generation unavailable in Production

Feb <var data-var='date'>16</var>, <var data-var='time'>14:30</var> GMT Resolved - Between 12:30 UK time and 15:45 UK time on 16th February 2026, some Categorized Bank Statement and Credit Model reports experienced unexpected latencies to complete. The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to generate reports, including the Credit Model and the Categorized Bank Statement reports, without disruption. If you are still affected by this issue, please contact support@codat.io.

Categorized Bank Statement and Credit Model report generation temporarily unavailable

Feb <var data-var='date'> 4</var>, <var data-var='time'>15:34</var> GMT Resolved - We have released a fix for this issue. Data connections can now be created to Shopify, for clients using custom apps. Please see our docs for updated linking instructions: https://docs.codat.io/integrations/commerce/shopify/commerce-shopify-custom-apps If you are still affected by this issue, please contact support@codat.io Feb <var data-var='date'> 3</var>, <var data-var='time'>09:35</var> GMT Identified - We have identified the issue and are in the process of implementing a fix. This incident will be updated as soon as we have successfully tested and rolled out a fix in production Feb <var data-var='date'> 2</var>, <var data-var='time'>10:56</var> GMT Investigating - We are currently investigating an issue where no new data connections can be linked to Shopify, for clients using custom apps. Existing connections are not affected. Affected users will notice that they are unable to generate a Shopify access token from their custom app during the linking process. This incident will be updated as soon as we have identified the issue.

Shopify - unable to create new connections

Jan <var data-var='date'>16</var>, <var data-var='time'>13:05</var> GMT Resolved - We have now successfully deployed a fix for this issue. Users of our system should now notice that for Xero connected companies, any bankTransactions datasets which had been failing with a Validation Error are now completing successfully. Jan <var data-var='date'>16</var>, <var data-var='time'>13:01</var> GMT Update - We are in the process of releasing a fix to this issue currently. This incident will be updated as soon as we have identified the issue, and no later than 14:05 Jan <var data-var='date'>16</var>, <var data-var='time'>11:55</var> GMT Identified - We have identified the root cause of the issue and are currently working on a fix. We hope to be able to release a fix to production in the very near future. This incident will be updated as soon as we have identified the issue, and no later than 13:05 Jan <var data-var='date'>16</var>, <var data-var='time'>11:03</var> GMT Investigating - We are actively investigating an issue whereby for Xero connected Companies, we are seeing a higher than expected number of validation errors on the BankTransactions dataset. Affected users will notice that companies who are synching BankTransactions datasets may have datasets fail with a Validation Error. This incident will be updated as soon as we have identified the issue, and no later than 12:05

Xero BankTransactions: High Number of Validation Errors

Dec <var data-var='date'>18</var>, <var data-var='time'>14:43</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to link to bank feeds without disruption. If you are still affected by this issue, please contact support@codat.io Dec <var data-var='date'>18</var>, <var data-var='time'>13:59</var> GMT Update - We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix, and no later than 14:58 GMT Dec <var data-var='date'>18</var>, <var data-var='time'>13:48</var> GMT Investigating - We are actively investigating an issue preventing users from progressing in the bank feeds link flow, when consumers of our service are leveraging our bank feeds link SDK. Affected users will notice that the calls to generate the OTP are failing with a CORS error, and that their end users are unable to progress beyond the 'configure your accounts' screen. This incident will be updated as soon as we have identified the issue, and no later than 14:47

Bank Feeds Link SDK: calls to generate OTP failing with a CORS error

Dec <var data-var='date'>18</var>, <var data-var='time'>10:30</var> GMT Resolved - Our monitoring flagged that between 10.20AM and 14.10 PM users were unable to download attachments. Affected users would have noticed that a 404 response being returned when making requests to attachments endpoints . The cause of the issue has been identified as an internal change in routing causing the request to not be passed correctly. Service has now been restored. If you are still affected by this issue, please contact support@codat.io for further assistance.

Error downloading attachments

Nov <var data-var='date'>27</var>, <var data-var='time'>07:15</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to push to Xero without disruption. If you are still affected by this issue, please contact support@codat.io Nov <var data-var='date'>26</var>, <var data-var='time'>14:36</var> GMT Monitoring - We have implemented a fix in production. Affected users should now notice that push operations are no longer failing with the previously seen error. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Nov <var data-var='date'>26</var>, <var data-var='time'>12:13</var> GMT Identified - We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix in production. Nov <var data-var='date'>26</var>, <var data-var='time'>09:41</var> GMT Investigating - We are actively investigating an issue causing a small number of push operations to Xero to incorrectly be marked as errored. Affected users will notice that a small number of push operations to Xero return an Internal server error with the following error message however the syncs were in fact successful and do not need to be retried. "'0x1F' is an invalid start of a value. Path: $ | LineNumber: 0 | BytePositionInLine: 0.". This incident will be updated as soon as we have identified the issue.

Small number of Xero pushes incorrectly showing as errored

Nov <var data-var='date'>18</var>, <var data-var='time'>15:30</var> GMT Resolved - Cloudflare have updated the incident as they have applied a fix. We can see that access to Codat services has returned to normal. If you're still experiencing issues please reach out to support@codat.io. Nov <var data-var='date'>18</var>, <var data-var='time'>13:51</var> GMT Update - The Cloudflare incident is ongoing and is continuing to affect our services intermittently. You can follow their status page for more detailed updates from their side https://www.cloudflarestatus.com Nov <var data-var='date'>18</var>, <var data-var='time'>11:53</var> GMT Update - We are continuing to monitor for any further issues. Nov <var data-var='date'>18</var>, <var data-var='time'>11:51</var> GMT Monitoring - Our monitoring has indicated that Codat services are intermittently temporarily unavailable starting at 11:36 GMT. We have identified the cause of the incident as a Cloudflare outage. Cloudflare have posted about this on their status page https://www.cloudflarestatus.com/. This incident will be updated as soon as service is restored and no later than 12:40 GMT.

Codat services unavailable - Cloudflare outage

Nov <var data-var='date'>11</var>, <var data-var='time'>14:57</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should now see Account Categorization proceed with the expected performance. If you are still affected by this issue, please contact support@codat.io Nov <var data-var='date'>11</var>, <var data-var='time'>14:38</var> GMT Monitoring - We have implemented a fix to the issue which was causing account categorization to occasionally run more slowly than expected. Affected users should now notice that account categorization completes within the expected time frame Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Nov <var data-var='date'>11</var>, <var data-var='time'>13:46</var> GMT Investigating - We are actively investigating an issue which is causing our account categorization service to run more slowly than usual, in some instances. Affected users will notice that our Account Categorization may be slower than usual. This incident will be updated as soon as we have identified the issue, and no later than 14:46

Account Categorization Performance Degradation.

Nov <var data-var='date'> 7</var>, <var data-var='time'>14:47</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to make API calls without disruption. If you are still affected by this issue, please contact support@codat.io Nov <var data-var='date'> 6</var>, <var data-var='time'>18:06</var> GMT Update - We are continuing to monitor for any further issues. Nov <var data-var='date'> 6</var>, <var data-var='time'>16:30</var> GMT Monitoring - We have implemented a fix and affected users should no longer be experiencing any errors or latency. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Nov <var data-var='date'> 6</var>, <var data-var='time'>14:29</var> GMT Investigating - We are actively investigating an issue with increased API latency and time outs. Affected users may notice that a small number of their operations failing with a 5xx error message. This incident will be updated as soon as we have identified the issue, and no later than 15:30

Intermittent API latency and failing with 5xx errors

Nov <var data-var='date'> 2</var>, <var data-var='time'>19:01</var> GMT Resolved - Our monitoring flagged that some features of our API were unavailable between 9:00 UTC and 18:16 UTC in Production. Affected users would have noticed that some API requests, linking new companies and syncing existing datasets failed, usually with a 5xx status code. The cause of the issue has been identified as a configuration issue. Service has now been restored. There is no further action for you or your end-users to take and you should retry any failing calls at your earliest convenience. If you are still affected by this issue, please contact support@codat.io for further assistance.

API unavailable in Production

Oct <var data-var='date'>20</var>, <var data-var='time'>08:30</var> BST Resolved - You may have noticed latencies and errors when linking and completing syncs on selected integrations this morning. This was caused by an Amazon (AWS) outage. You can find more details about this incident on Amazon's status page here: https://health.aws.amazon.com/health/status While Codat infrastructure and services were not directly affected, linking and syncing data from third-party integrations that use AWS to provide their service has been impacted. The issue has now been resolved and the service has been restored by Amazon for most third-party affected. There is no further action required from you or your clients as syncs have now resumed as per any schedules. Any ad-hoc operations and onboarding flows can be retried at your earliest convenience. If you are still experiencing an issue, contact support@codat.io for further assistance.

AWS outage affecting third-party availability

API Connectivity

Portal

Link

Webhooks & Alerts

General Connectivity & Portal

Bank Feeds Connectivity

QuickBooks Online Bank Feeds

Sage Bank Feeds

FreeAgent Bank Feeds

Xero Bank Feeds

Exact Bank Feeds

Bank Feeds

Lending Connectivity

Clear Books

Dynamics 365 Business Central

Exact Online

FreeAgent

FreshBooks

MYOB Business

Oracle NetSuite

QuickBooks Desktop

QuickBooks Online

Sage 50

Sage 200 Cloud

Sage Business Cloud Accounting

Sage Intacct

Wave

Xero

Zoho Books

Plaid

TrueLayer

Amazon Seller Central

BigCommerce

Clover

Lightspeed Restaurant K-Series

Mollie

PayPal

PrestaShop

Shopify

Square

Stripe

SumUp

WooCommerce

Zettle

Chargebee

Enhanced Cashflow Report Generation and Download

Enhanced Financials Report Generation and Download

Enhanced Invoices Report Generation and Download

Audit Report Generation and Download

Aged Debtors Report Generation and Download

Aged Creditors Report Generation and Download

Liabilities Report Generation and Download

Credit Model Report Generation and Download

Lending

Spend Insights Connectivity

MS Dynamics 365 BC

Spend Analysis Report Generation and Download

Spend Summary Report Generation and Download

Spend Insights

Sync For Commerce Connectivity

Sync For Commerce

Sync For Expenses Connectivity

Expenses

Bill Pay (Sync) Connectivity

Bill Pay (sync)

Bill Pay (async) Connectivity

Bill Pay (async)

Sync For Payroll Connectivity

Sync For Payroll

Xero - Accounting API (External)

QuickBooks Online - Intuit Developer Group Services

QuickBooks Online - Accounting API (External)

Shopify API & Mobile

Stripe API

BigCommerce API & Webhooks

Plaid API - Production

Svix - Webhooks

Email Alerts Message Delivery (External)

Mailgun (Email notifications & alerts)

npm Package installation

GitHub Packages

Python Infrastructure pypi.org - General

Auth0 User Authentication

Auth0 Machine to Machine Authentication

Auth0 Management API

Auth0 Email Delivery

Third-party integrations and infrastructures

Clearbooks

Exact

Freshbooks

MYOB

Sage 200cloud

Legacy - Accounting API

Legacy - Banking API

Big Commerce

Lightspeed Restaurant (Series K)

Legacy - Commerce API

Schedule

NetSuite

Custom Product 91D68E9E-9C28-4C9A-9803-73A92AC3F748

Custom Product CF3A11B4-ACC3-4BC2-B498-64A9F638311C

OneUp

Custom Product C9ECB109-8C62-4595-9130-849B710CFE14

Sage 200

Custom Product F74BC050-CE30-4CF3-A1F6-7D5F3B5F7BD9

Custom Product 12BCD5ED-1A48-46E6-BD71-2D638FE5B7BF

Custom Product 55B5F014-36F3-4EC4-84B2-6B6DAF2960B8

Codat

Is Codat down?

Codat status is UP

Lastest published events

Intermittent API errors

Users unable to create companies with Tags

QuickBooks Desktop Push Operation Outage

Codat Services, Components and Regions

Recent Codat events

Intermittent API errors

Users unable to create companies with Tags

QuickBooks Desktop Push Operation Outage

TrueLayer call backs routing to "Unknown Destination" error page.

Plaid banking-transaction fetches failing intermittently.

QuickBooks Desktop Push Operations not moving beyond Pending

Get your FREE account now,
5 monitors included!

Is Codat down?

Codat status is UP

Lastest published events

Intermittent API errors

Users unable to create companies with Tags

QuickBooks Desktop Push Operation Outage

Codat Services, Components and Regions

Recent Codat events

Intermittent API errors

Users unable to create companies with Tags

QuickBooks Desktop Push Operation Outage

TrueLayer call backs routing to "Unknown Destination" error page.

Plaid banking-transaction fetches failing intermittently.

QuickBooks Desktop Push Operations not moving beyond Pending

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!