Historial de interrupciones de Codat

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.

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.

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

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.

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.

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

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

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.

This incident has been resolved. Pushing to QBD is now working as expected.

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.

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.

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

We are continuing to investigate this issue.

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

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.

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

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.

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.

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

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

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.

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

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.

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.

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.

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.

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

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.

We are continuing to investigate this issue.

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.

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

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.

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.

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.

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.

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.

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

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.

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.

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

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

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

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

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

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.

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

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

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

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.

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.

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.

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.

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