Codat 中断历史

1. 2026年8月24日 UTC 13:49identified

   我们意识到一个影响到我们一些整合和同步服务的问题,目前正在实施一个纠正该问题的解决方案. 对这些服务的要求目前还存在错误。 重试会还原同样的错误 直到我们解决这个问题, 所以不需要你采取行动。 一旦恢复服务,排队同步将自动恢复。 所有其他整合和服务都正常运行。 我们一旦有更多要分享的,就会更新这个页面. 一旦我们成功测试并推出一个固定装置, 并且不迟于格林尼治平时4:.

2. 2026年8月24日 UTC 14:36monitoring

   我们已经执行了一项固定措施。 受影响的用户现在应该注意到,他们再次能够正常使用受影响的服务。 排队同步将自动恢复 。 我们的小组继续监测该平台,以确保持续稳定。 若遇到任何问题,请联系@codat.io,以获得进一步援助.

3. 2026年8月24日 UTC 15:46resolved

   事件现已解决,持续监测显示平台已恢复正常稳定. 以前受影响的所有用户都应能够使用受影响的服务而不受干扰。 如果您仍受此问题影响,请联系支持@codat.io

自动翻译自官方事件更新。

1. 2026年8月11日 UTC 15:00investigating

   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

2. 2026年8月11日 UTC 15:09monitoring

   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.

3. 2026年8月11日 UTC 15:32resolved

   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]

1. 2026年8月5日 UTC 09:01investigating

   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.

2. 2026年8月5日 UTC 09:18monitoring

   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.

3. 2026年8月5日 UTC 15:47resolved

   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]

1. 2026年7月27日 UTC 15:08investigating

   我们正积极调查一个阻止用户使用Codat门户网站的问题, 受影响的用户会注意到,他们无法在没有错误或登录到Codat门户网站的情况下调用Codat Api. 此事一旦查明,即予更新,最迟于17:07

2. 2026年7月27日 UTC 15:09monitoring

   我们实施了彻底停电的解决方案。 受影响的用户现在应该注意到,他们再次能够正常地使用Codat门户和Api。 我们的小组继续监测该平台,以确保持续稳定。 若遇到任何问题,请联系@codat.io,以获得进一步援助.

3. 2026年7月27日 UTC 18:33resolved

   该事件现已得到解决,因为持续监测显示该平台已恢复正常稳定。 你可能注意到了协调世界时14:54-15:06时Codat API或Codat门户网站的错误 如果您仍受此问题影响,请联系支持@codat.io

自动翻译自官方事件更新。

1. 2026年7月24日 UTC 12:43investigating

   我们正在积极调查一个阻止用户登录Codat门户网站的问题,并向我们的公共API发出API电话. 受影响的用户会注意到,他们无法登录Codat网络门户,并拨打API电话. 这两种情况都会出现500个类别错误。 此事一经查清,将予更新,最迟至14:40

2. 2026年7月24日 UTC 12:48monitoring

   我们已经对停电进行了补救。 Codat的服务和门户网站现在应再次开放。 我们的小组继续监测该平台,以确保持续稳定。 若遇到任何问题,请联系@codat.io,以获得进一步援助.

3. 2026年7月24日 UTC 12:57resolved

   事件现已解决,持续监测显示平台已恢复正常稳定. 如果您仍受此问题影响,请联系支持@codat.io

自动翻译自官方事件更新。

1. 2026年7月22日 UTC 14:11investigating

   我们正在积极调查一个问题 阻止用户拉动和推进数据到Xero。 受影响的用户会注意到,所有Xero Push and Pull Operations都会导致出错. 此事一经查明,即会更新,最迟于16:09

2. 2026年7月22日 UTC 14:34monitoring

   推和拉为Xero集成 现在又如预期的那样工作了 我们的小组继续监测该平台,以确保持续稳定。 若遇到任何问题,请联系@codat.io,以获得进一步援助.

3. 2026年7月22日 UTC 15:37resolved

   这一事件现已得到解决.

自动翻译自官方事件更新。

1. 2026年7月24日 UTC 09:55investigating

   根据https://status.codat.io/incidents/92vdwfbdrw97,我们仍在观察一些Xero故障。 受影响的用户会注意到,他们将操作推向或拉到Xero时会因Auth - 相关的错误而失败. 错误似乎是短暂的,因此建议我们的用户重试任何失败的操作.

2. 2026年7月24日 UTC 10:48investigating

   我们已查明了事件的原因,并正在执行一项补救措施。 一旦我们成功测试并推出一个固定器 并不迟于12:48 UK Time

3. 2026年7月24日 UTC 11:25investigating

   我们已查明了事件的原因,并正在执行一项补救措施。 一旦我们成功测试并推出固定装置,将立即更新这一事件,该固定装置将不迟于13:25

4. 2026年7月28日 UTC 08:13identified

   我们正继续与我们在Xero的伙伴合作,以缓解这一问题。 根据我们的观察,故障是断断续续的,所以任何没有如所期望的那样成功的推动或拉动操作都可以被重审. 一旦我们相信已经部署了一个固定方案,我们将更新现状网页,以反映这一点.

5. 2026年7月28日 UTC 09:55identified

   我们正在继续与我们的伙伴Xero合作,并且已经确定了一项决议。 双方都希望尽快缓解这一问题,并尽快执行解决办法。 根据我们的观察,故障是断断续续的,所以任何没有如所期望的那样成功的推动或拉动操作都可以被重审. 一旦我们相信已经部署了一个固定方案,我们将更新现状网页,以反映这一点.

6. 2026年7月28日 UTC 15:56resolved

   事件现已解决,持续监测显示平台已恢复正常稳定. 所有先前受到影响的用户都应能够按预期将数据从Xero推到Xero。 如果您仍受此问题影响,请联系支持@codat.io

自动翻译自官方事件更新。

1. 2026年7月17日 UTC 12:06investigating

   我们正在积极调查一个问题,防止一部分用户将Xero公司与Codat公司联系起来。 受影响的用户会注意到,在链接流中被重定向到Xero时,会显示一个Xero出错的页面,有500个出错代码. 此事一经查清,将立即更新,并不迟于14:05

2. 2026年7月17日 UTC 12:07investigating

   在继续调查根源的同时,我们确定了一种缓解措施。 用户现在应该能够把Xero公司与Codat联系起来。 一旦我们成功测试并推出永久解决方案,这一事件将立即得到更新.

3. 2026年7月17日 UTC 12:07identified

   在继续调查根源的同时,我们确定了一种缓解措施。 用户现在应该能够把Xero公司与Codat联系起来。 一旦我们成功测试并推出永久解决方案,这一事件将立即得到更新.

4. 2026年7月17日 UTC 15:01resolved

   事件现已解决,持续监测显示平台已恢复正常稳定. 以前受到影响的所有用户现在都应能够再次将其Xero公司与Codat连接起来。 如果您仍受此问题影响,请联系支持@codat.io

自动翻译自官方事件更新。

1. 2026年6月22日 UTC 15:22investigating

   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.

2. 2026年6月22日 UTC 15:43monitoring

   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.

3. 2026年6月22日 UTC 18:25resolved

   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]

1. 2026年6月2日 UTC 14:01identified

   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.

2. 2026年6月2日 UTC 14:07monitoring

   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.

3. 2026年6月2日 UTC 14:45resolved

   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]

1. 2026年5月29日 UTC 14:03investigating

   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

2. 2026年5月29日 UTC 14:07monitoring

   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.

3. 2026年5月29日 UTC 14:50resolved

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

1. 2026年5月29日 UTC 11:17resolved

   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.

1. 2026年6月3日 UTC 14:42resolved

   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.

1. 2026年4月21日 UTC 15:59investigating

   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

2. 2026年4月21日 UTC 16:02investigating

   We are continuing to investigate this issue.

3. 2026年4月21日 UTC 17:41identified

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

4. 2026年4月21日 UTC 18:51monitoring

   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.

5. 2026年4月22日 UTC 12:24resolved

   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]

1. 2026年3月26日 UTC 10:47investigating

   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.

2. 2026年3月26日 UTC 11:21monitoring

   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.

3. 2026年3月26日 UTC 15:23resolved

   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]

1. 2026年3月19日 UTC 12:49investigating

   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

2. 2026年3月19日 UTC 13:09monitoring

   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.

3. 2026年3月19日 UTC 13:22resolved

   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]

1. 2026年3月13日 UTC 14:12resolved

   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.

1. 2026年3月13日 UTC 10:05resolved

   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.

1. 2026年3月6日 UTC 10:26investigating

   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.

2. 2026年3月6日 UTC 10:38monitoring

   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.

3. 2026年3月6日 UTC 14:53resolved

   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]

1. 2026年2月24日 UTC 10:34investigating

   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.

2. 2026年2月24日 UTC 10:38investigating

   We are continuing to investigate this issue.

3. 2026年2月24日 UTC 11:10monitoring

   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.

4. 2026年2月24日 UTC 14:59resolved

   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]