Codat outage history

We're aware of an issue affecting a number of our integrations and sync services and are currently implementing a fix to remediate the issue. Requests to these services are currently returning errors. Retrying will return the same error until we've fixed the issue, so no action is needed from you. Queued syncs will resume automatically once service is restored. All other integrations and services are operating normally. We'll update this page as soon as we have more to share. This incident will be updated as soon as we have successfully tested and rolled out a fix, and no later than 4:00PM GMT.

We have implemented a fix. Affected users should now notice that they are again able to use the affected services as normal. Queued syncs will resume automatically. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues 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 use affected services without disruption. If you are still affected by this issue, please contact [email protected]

We are actively investigating an issue preventing users from accessing the Company reports page. Affected users will notice that when attempting to navigate to the Lending > Reports page for a given company, the web page will show a generic 'Oh no! Something went wrong' error. This incident will be updated as soon as we have identified the issue, and no later than 17:00

We have implemented a fix. Affected users should now notice that they are now able to access the reports page without an error. You may need to perform a hard refresh of your browser. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues 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 load the reports page. If you are still affected by this issue, please contact [email protected]

We are actively investigating an issue which will be causing our reports generation and sync for expenses transactions pushes to take longer than normal. Affected users will notice that when they attempt to generate a report, it may take several minutes longer than usual.

Affected users should now notice that reports generation and sync for expenses transactions pushes run much more quickly. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues 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 generate reports and sync expenses without unexpected latencies. If you are still affected by this issue, please contact [email protected]

We are actively investigating an issue preventing users from both using the Codat portal and calling our public facing APIs. Affected users will notice that they are unable to call the Codat Api without an error or login to the Codat portal. This incident will be updated as soon as we have identified the issue, and no later than 17:07

We have implemented a fix to the complete outage. Affected users should now notice that they are again able to use the Codat portal and Api as normal. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact [email protected] for further assistance.

The incident has now been resolved, as ongoing monitoring has shown the platform has returned to normal stability. You may have noticed errors with the Codat API or the Codat Portal from 14:54-15:06 UTC If you are still affected by this issue, please contact [email protected]

We are actively investigating an issue preventing users from logging into the Codat Portal and making API calls to our Public API. Affected users will notice that they are unable to log into the Codat web portal and make API calls. There would be a 500 category error surfaced in both cases. This incident will be updated as soon as we have identified the issue, and no later than 14:40

We have implemented a fix for the outage. Codat's services and Portal should now be accessible again. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please 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]

We are actively investigating an issue preventing users from Pulling and Pushing Data to Xero. Affected users will notice that all Xero Push and Pull Operations result in an error. This incident will be updated as soon as we have identified the issue, and no later than 16:09

Push and Pull For the Xero integration are now working again as expected. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact [email protected] for further assistance.

This incident is now resolved.

Following on from Incident https://status.codat.io/incidents/92vdwfbdrw97, we are still observing some Xero failures. Affected users will notice that their push or pull operations to Xero are failing with an Auth - related error. The errors appear to be transient, so our users are advised to retry any failed operations.

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 12:48 UK Time

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 the fix, which will be no later than 13:25

We are continuing to work with our partners at Xero in an attempt to mitigate this issue. As per our observations, the failures are intermittent, so any push or pull operations which don't succeed as expected can be retried. As soon as we are confident that a fix has been deployed, we will update the status page to reflect this.

We are continuing to work with our partner Xero, and a resolution has been identified. Both parties are looking to assuage the problem asap and a resolution should be implemented as soon as possible. As per our observations, the failures are intermittent, so any push or pull operations which don't succeed as expected can be retried. As soon as we are confident that a fix has been deployed, we will update the status page to reflect this.

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 and pull data from and to Xero as expected. If you are still affected by this issue, please contact [email protected]

We are actively investigating an issue preventing a subset of users from linking their Xero companies to Codat. Affected users will notice that upon being redirected to Xero during the link flow, a Xero error page will show, with a 500 error code. This incident will be updated as soon as we have identified the issue, and no later than 14:05

We have identified a mitigation whilst we continue to investigate the root cause. Users should now be able to link Xero companies to Codat. This incident will be updated as soon as we have successfully tested and rolled out a permanent fix.

We have identified a mitigation whilst we continue to investigate the root cause. Users should now be able to link Xero companies to Codat. This incident will be updated as soon as we have successfully tested and rolled out a permanent fix.

The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should now again be able to connect their Xero Companies to Codat. If you are still affected by this issue, please contact [email protected]

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

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

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 [email protected] 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 [email protected] 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 [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 successfully complete push operations to QuickBooks Desktop without disruption. If you are still affected by this issue, please contact [email protected]

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

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

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 [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 push attachments to QBO Sandbox without disruption. If you are still affected by this issue, please contact [email protected]

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 [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 generate Credit Model and Categorized Bank Statements reports in Production without disruption. If you are still affected by this issue, please contact [email protected]