Codat Outage History

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

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 view the Data of their Companies in the Codat portal. If you are still affected by this issue, please contact [email protected]

The incident has now been resolved, the root cause of the problem was an underlying issue with our 3rd party Cloud Services provider and has been escalated appropriately on their side. Ongoing monitoring has shown that the mitigations we have put in place, returned our platform to normal stability. 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 push operations to the Xero Accounting system should now complete within a few minutes, as they ordinarily do. 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 no longer notice missing line items following completion of Sage Intacct Bills datasets. 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 fetch data from a Shopify connection 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 Quickbooks Desktop platform has returned to normal stability. All users previously affected should be able to pull data without disruption. If you are still affected by this issue, please contact [email protected]

Our monitoring flagged that a small percentage of requests failed with 5XX status codes or timeouts between 8:02BST and 08:32BST. The cause of the issue has been identified as a traffic being directed to a bad application instance. Service has now been restored. If you are still affected by this issue, please contact [email protected] for further assistance.

Our monitoring flagged that a small minority of QuickBooks Desktop fetch operations may have completed more slowly than expected. An even smaller subset of these eventually moved into a FetchError state. We have now fully restored this functionality. Consumers of the Codat system should be able to requeue all QBD datasets and expect them to complete as expected. The incident began at approximately 15:13 UK time and was fully assuaged by 16:35. 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 sync data without disruption. If you are still affected by this issue, please contact [email protected]

Our monitoring flagged that the Codat Portal and API were down between 16:34 and 16:41 UK time. Affected users would have noticed that accessing the Codat Portal or calling the Codat API returned intermittently 500s and 404s error codes. The cause of the issue has been identified as a temporary unavailability of our servers. We rolled back and redeployed our hosted apps and the service was restored successfully. If you are still affected by this issue, please contact [email protected] for further assistance.

This incident has been 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 and we have requeued any datasets that failed with InternalErrors previously. 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. The cause of the issue has been identified as code released by a third-party and resulting in an error. The affected third-party code has been rolledback successfully. All users previously affected should be able to attach files to bills and expenses in their FreeAgent companies without disruption. If you are still affected by this issue, please contact [email protected]

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]

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 push new data via the Codat API for their QBO companies without disruption. If you are still affected by this issue, please contact [email protected]