Codat Outage History

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 [email protected] 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 [email protected]

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

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 [email protected]

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 [email protected]

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 [email protected]

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 [email protected] 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.

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 [email protected]

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 [email protected]

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 [email protected].

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 [email protected]

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 [email protected].

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 [email protected]

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.

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 [email protected] 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 link to bank feeds without disruption. If you are still affected by this issue, please contact [email protected]

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 [email protected]

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 [email protected].

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 [email protected]

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 [email protected]

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 [email protected] for further assistance.

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 [email protected] for further assistance.

The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. If you are still affected by this issue, please contact [email protected]