Histórico de interrupções do Codat

1. 24 Eost 2026 da 13:49 UTCidentified

   Estamos cientes de um problema que afeta uma série de nossas integrações e serviços de sincronização e estamos atualmente implementando uma solução para corrigir o problema. Os pedidos a estes serviços estão atualmente retornando erros. Retentar irá retornar o mesmo erro até que tenhamos corrigido o problema, então nenhuma ação é necessária de você. As sincronizações em filas serão retomadas automaticamente assim que o serviço for restaurado. Todas as outras integrações e serviços funcionam normalmente. Atualizaremos esta página assim que tivermos mais para compartilhar. Este incidente será atualizado assim que tivermos testado e feito uma correção com sucesso, e o mais tardar às 16:00 GMT.

2. 24 Eost 2026 da 14:36 UTCmonitoring

   Implementámos uma solução. Os utilizadores afectados devem agora notar que são novamente capazes de utilizar os serviços afectados como normais. As sincronizaçãos em fila serão retomadas automaticamente. Nossas equipes continuam monitorando a plataforma para garantir a estabilidade contínua. Se você tiver algum problema, entre em contato com [email protected] para mais assistência.

3. 24 Eost 2026 da 15:46 UTCresolved

   O incidente foi agora resolvido, o monitoramento contínuo mostrou que a plataforma voltou à estabilidade normal. Todos os utilizadores anteriormente afectados devem poder utilizar os serviços afectados sem perturbações. Se você ainda for afetado por este problema, entre em contato com [email protected]

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Eost 2026 da 15:00 UTCinvestigating

   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. 11 Eost 2026 da 15:09 UTCmonitoring

   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. 11 Eost 2026 da 15:32 UTCresolved

   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. 5 Eost 2026 da 09:01 UTCinvestigating

   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. 5 Eost 2026 da 09:18 UTCmonitoring

   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. 5 Eost 2026 da 15:47 UTCresolved

   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. 27 Gouere 2026 da 15:08 UTCinvestigating

   Estamos investigando ativamente um problema que impede os usuários de usar o portal Codat e ligar para nossas APIs voltadas para o público. Usuários afetados notarão que eles são incapazes de chamar o Api Codat sem um erro ou login no portal Codat. Este incidente será actualizado assim que tivermos identificado o problema, e o mais tardar às 17:07

2. 27 Gouere 2026 da 15:09 UTCmonitoring

   Implementámos uma solução para a falha total. Os usuários afetados devem agora notar que eles são novamente capazes de usar o portal Codat e Api como normal. Nossas equipes continuam monitorando a plataforma para garantir a estabilidade contínua. Se você tiver algum problema, entre em contato com [email protected] para mais assistência.

3. 27 Gouere 2026 da 18:33 UTCresolved

   O incidente foi agora resolvido, uma vez que o acompanhamento contínuo mostrou que a plataforma voltou à estabilidade normal. Você pode ter notado erros com a API Codat ou o Portal Codat de 14:54-15:06 UTC Se você ainda for afetado por este problema, entre em contato com [email protected]

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gouere 2026 da 12:43 UTCinvestigating

   Estamos investigando ativamente um problema que impede os usuários de entrar no Portal Codat e fazer chamadas de API para nossa API pública. Usuários afetados notarão que eles não são capazes de entrar no portal Web Codat e fazer chamadas API. Haveria um erro de categoria de 500 em ambos os casos. Este incidente será actualizado logo que tenhamos identificado a questão, e o mais tardar às 14:40

2. 24 Gouere 2026 da 12:48 UTCmonitoring

   Implementámos uma solução para a falha. Os serviços e o Portal de Codat devem ser novamente acessíveis. Nossas equipes continuam monitorando a plataforma para garantir a estabilidade contínua. Se você tiver algum problema, entre em contato com [email protected] para mais assistência.

3. 24 Gouere 2026 da 12:57 UTCresolved

   O incidente foi agora resolvido, o monitoramento contínuo mostrou que a plataforma voltou à estabilidade normal. Se você ainda for afetado por este problema, entre em contato com [email protected]

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gouere 2026 da 14:11 UTCinvestigating

   Estamos ativamente investigando um problema que impede os usuários de puxar e empurrar dados para o Xero. Usuários afetados notarão que todas as operações Xero Push and Pull resultam em um erro. Este incidente será actualizado assim que tivermos identificado o problema, e o mais tardar às 16:09

2. 22 Gouere 2026 da 14:34 UTCmonitoring

   Empurre e puxe Para a integração do Xero agora estão trabalhando novamente como esperado. Nossas equipes continuam monitorando a plataforma para garantir a estabilidade contínua. Se você tiver algum problema, entre em contato com [email protected] para mais assistência.

3. 22 Gouere 2026 da 15:37 UTCresolved

   Este incidente está agora resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gouere 2026 da 09:55 UTCinvestigating

   Após o incidente https://status.codat.io/incidentes/92vdwfbdrw97, ainda estamos observando algumas falhas do Xero. Os usuários afetados notarão que suas operações de push ou puxão para o Xero estão falhando com um erro relacionado ao Auth. Os erros parecem ser transitórios, então nossos usuários são aconselhados a tentar novamente quaisquer operações falhadas.

2. 24 Gouere 2026 da 10:48 UTCinvestigating

   Identificámos a causa do incidente e estamos actualmente a implementar uma solução para resolver a questão. Este incidente será atualizado assim que tivermos testado e executado com sucesso uma correção e, o mais tardar, 12:48 UK Time

3. 24 Gouere 2026 da 11:25 UTCinvestigating

   Identificámos a causa do incidente e estamos actualmente a implementar uma solução para resolver a questão. Este incidente será atualizado assim que tivermos testado e executado com sucesso a correção, que será o mais tardar 13:25

4. 28 Gouere 2026 da 08:13 UTCidentified

   Continuamos a trabalhar com os nossos parceiros na Xero na tentativa de mitigar esta questão. De acordo com nossas observações, as falhas são intermitentes, então qualquer operação de push ou pull que não tenha sucesso como esperado pode ser novamente testada. Assim que estivermos confiantes de que uma correção foi implantada, atualizaremos a página de status para refletir isso.

5. 28 Gouere 2026 da 09:55 UTCidentified

   Continuamos a trabalhar com o nosso parceiro Xero, e foi identificada uma resolução. Ambas as partes procuram resolver o problema o mais rapidamente possível e uma resolução deverá ser implementada o mais rapidamente possível. De acordo com nossas observações, as falhas são intermitentes, então qualquer operação de push ou pull que não tenha sucesso como esperado pode ser novamente testada. Assim que estivermos confiantes de que uma correção foi implantada, atualizaremos a página de status para refletir isso.

6. 28 Gouere 2026 da 15:56 UTCresolved

   O incidente foi agora resolvido, o monitoramento contínuo mostrou que a plataforma voltou à estabilidade normal. Todos os usuários anteriormente afetados devem ser capazes de empurrar e puxar dados de e para Xero, como esperado. Se você ainda for afetado por este problema, entre em contato com [email protected]

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Gouere 2026 da 12:06 UTCinvestigating

   Estamos a investigar activamente um problema que impede um subconjunto de utilizadores de ligar as suas empresas Xero à Codat. Usuários afetados notarão que ao serem redirecionados para Xero durante o fluxo de link, uma página de erro Xero será exibida, com um código de erro de 500. Este incidente será actualizado assim que tivermos identificado o problema, e o mais tardar às 14:05

2. 17 Gouere 2026 da 12:07 UTCinvestigating

   Identificamos uma mitigação enquanto continuamos a investigar a causa raiz. Os usuários devem agora ser capazes de ligar as empresas Xero à Codat. Este incidente será atualizado assim que tivermos testado com sucesso e feito uma correção permanente.

3. 17 Gouere 2026 da 12:07 UTCidentified

   Identificamos uma mitigação enquanto continuamos a investigar a causa raiz. Os usuários devem agora ser capazes de ligar as empresas Xero à Codat. Este incidente será atualizado assim que tivermos testado com sucesso e feito uma correção permanente.

4. 17 Gouere 2026 da 15:01 UTCresolved

   O incidente foi agora resolvido, o monitoramento contínuo mostrou que a plataforma voltou à estabilidade normal. Todos os usuários anteriormente afetados devem novamente ser capazes de conectar suas empresas Xero à Codat. Se você ainda for afetado por este problema, entre em contato com [email protected]

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Mezheven 2026 da 15:22 UTCinvestigating

   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. 22 Mezheven 2026 da 15:43 UTCmonitoring

   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. 22 Mezheven 2026 da 18:25 UTCresolved

   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. 2 Mezheven 2026 da 14:01 UTCidentified

   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. 2 Mezheven 2026 da 14:07 UTCmonitoring

   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. 2 Mezheven 2026 da 14:45 UTCresolved

   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. 29 Mae 2026 da 14:03 UTCinvestigating

   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. 29 Mae 2026 da 14:07 UTCmonitoring

   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. 29 Mae 2026 da 14:50 UTCresolved

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

1. 29 Mae 2026 da 11:17 UTCresolved

   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. 3 Mezheven 2026 da 14:42 UTCresolved

   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. 21 Ebrel 2026 da 15:59 UTCinvestigating

   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. 21 Ebrel 2026 da 16:02 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 Ebrel 2026 da 17:41 UTCidentified

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

4. 21 Ebrel 2026 da 18:51 UTCmonitoring

   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. 22 Ebrel 2026 da 12:24 UTCresolved

   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. 26 Meurzh 2026 da 10:47 UTCinvestigating

   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. 26 Meurzh 2026 da 11:21 UTCmonitoring

   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. 26 Meurzh 2026 da 15:23 UTCresolved

   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. 19 Meurzh 2026 da 12:49 UTCinvestigating

   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. 19 Meurzh 2026 da 13:09 UTCmonitoring

   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. 19 Meurzh 2026 da 13:22 UTCresolved

   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. 13 Meurzh 2026 da 14:12 UTCresolved

   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. 13 Meurzh 2026 da 10:05 UTCresolved

   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. 6 Meurzh 2026 da 10:26 UTCinvestigating

   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. 6 Meurzh 2026 da 10:38 UTCmonitoring

   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. 6 Meurzh 2026 da 14:53 UTCresolved

   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. 24 Cʼhwevrer 2026 da 10:34 UTCinvestigating

   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. 24 Cʼhwevrer 2026 da 10:38 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 Cʼhwevrer 2026 da 11:10 UTCmonitoring

   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. 24 Cʼhwevrer 2026 da 14:59 UTCresolved

   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]