Historial de interrupciones de Codat

1. August 24, 2026 at 1:49 PM UTCidentified

   Somos conscientes de un problema que afecta a varias de nuestras integraciones y servicios de sincronización y actualmente estamos implementando una solución para remediar el tema. Las solicitudes a estos servicios están devolviendo errores. Retrying devolverá el mismo error hasta que hayamos arreglado el problema, así que no se necesita acción de ti. Los sincronizados se reanudarán automáticamente una vez restaurado el servicio. Todas las demás integraciones y servicios funcionan normalmente. Actualizaremos esta página tan pronto como tengamos más que compartir. Este incidente se actualizará tan pronto como hayamos probado con éxito y lanzado una solución, y a más tardar las 4:00PM GMT.

2. August 24, 2026 at 2:36 PM UTCmonitoring

   Hemos implementado una solución. Los usuarios afectados deben notar ahora que pueden volver a utilizar los servicios afectados como normales. Los sincronizados se reanudarán automáticamente. Nuestros equipos siguen vigilando la plataforma para garantizar la estabilidad continua. Si experimenta algún problema, póngase en contacto con [email protected] para recibir más asistencia.

3. August 24, 2026 at 3:46 PM UTCresolved

   El incidente ya se ha resuelto, la vigilancia continua ha demostrado que la plataforma ha vuelto a la estabilidad normal. Todos los usuarios anteriormente afectados deben poder utilizar servicios afectados sin perturbaciones. Si sigues afectado por este problema, contacta con [email protected]

Traducido automáticamente desde la actualización oficial del incidente.

1. August 11, 2026 at 3:00 PM 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. August 11, 2026 at 3:09 PM 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. August 11, 2026 at 3:32 PM 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. August 5, 2026 at 9:01 AM 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. August 5, 2026 at 9:18 AM 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. August 5, 2026 at 3:47 PM 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. July 27, 2026 at 3:08 PM UTCinvestigating

   Estamos investigando activamente un problema que impide a los usuarios utilizar el portal Codat y llamando a nuestro público frente a APIs. Los usuarios afectados notarán que no pueden llamar al Codat Api sin un error o acceder al portal Codat. Este incidente se actualizará tan pronto como hayamos identificado el problema, y a más tardar 17:07

2. July 27, 2026 at 3:09 PM UTCmonitoring

   Hemos implementado una solución a la salida completa. Los usuarios afectados deben notar ahora que están de nuevo capaces de utilizar el portal Codat y Api como normal. Nuestros equipos siguen vigilando la plataforma para garantizar la estabilidad continua. Si experimenta algún problema, póngase en contacto con [email protected] para recibir más asistencia.

3. July 27, 2026 at 6:33 PM UTCresolved

   El incidente ya se ha resuelto, ya que la vigilancia continua ha demostrado que la plataforma ha vuelto a la estabilidad normal. Usted puede haber notado errores con la API Codat o el Portal Codat de 14:54-15:06 UTC Si sigues afectado por este problema, contacta con [email protected]

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 12:43 PM UTCinvestigating

   Estamos investigando activamente un problema que impide a los usuarios iniciar sesión en el Portal de Codat y hacer llamadas de API a nuestra API pública. Los usuarios afectados notarán que no pueden acceder al portal web de Codat y hacer llamadas de API. En ambos casos se produciría un error de 500 categorías. Este incidente se actualizará tan pronto como hayamos identificado el problema, y a más tardar 14:40

2. July 24, 2026 at 12:48 PM UTCmonitoring

   Hemos implementado una solución para la salida. Los servicios de Codat y Portal ahora deben ser accesibles de nuevo. Nuestros equipos siguen vigilando la plataforma para garantizar la estabilidad continua. Si experimenta algún problema, póngase en contacto con [email protected] para recibir más asistencia.

3. July 24, 2026 at 12:57 PM UTCresolved

   El incidente ya se ha resuelto, la vigilancia continua ha demostrado que la plataforma ha vuelto a la estabilidad normal. Si sigues afectado por este problema, contacta con [email protected]

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 2:11 PM UTCinvestigating

   Estamos investigando activamente un problema que impide a los usuarios de Pulling y Pushing Data a Xero. Los usuarios afectados notarán que todos los Xero Push y Pull Operations resultan en un error. Este incidente se actualizará tan pronto como hayamos identificado el problema, y a más tardar 16:09

2. July 22, 2026 at 2:34 PM UTCmonitoring

   Empujar y tirar Para la integración Xero ahora están trabajando de nuevo como se espera. Nuestros equipos siguen vigilando la plataforma para garantizar la estabilidad continua. Si experimenta algún problema, póngase en contacto con [email protected] para recibir más asistencia.

3. July 22, 2026 at 3:37 PM UTCresolved

   Este incidente ya está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 9:55 AM UTCinvestigating

   Siguiendo el ejemplo https://status.codat.io/incidents/92vdwfbdrw97, seguimos observando algunos fallos de Xero. Los usuarios afectados notarán que sus operaciones de empuje o de atracción a Xero están fallando con un error relacionado con Auth. Los errores parecen ser transitorios, por lo que a nuestros usuarios se les recomienda reintentar cualquier operación fallida.

2. July 24, 2026 at 10:48 AM UTCinvestigating

   Hemos identificado la causa del incidente y actualmente estamos implementando una solución para remediar la cuestión. Este incidente se actualizará tan pronto como hayamos probado y lanzado con éxito una solución y a más tardar 12:48 UK Time

3. July 24, 2026 at 11:25 AM UTCinvestigating

   Hemos identificado la causa del incidente y actualmente estamos implementando una solución para remediar la cuestión. Este incidente se actualizará tan pronto como hayamos probado y lanzado con éxito la solución, que será a más tardar 13:25

4. July 28, 2026 at 8:13 AM UTCidentified

   Continuamos trabajando con nuestros socios en Xero en un intento de mitigar este problema. Según nuestras observaciones, los fracasos son intermitentes, por lo que cualquier operación de empuje o de empuje que no tenga éxito como se espera puede ser retrigado. Tan pronto como tengamos confianza en que se ha implementado una solución, actualizaremos la página de estado para reflejar esto.

5. July 28, 2026 at 9:55 AM UTCidentified

   Continuamos trabajando con nuestro socio Xero, y se ha identificado una resolución. Ambas partes están tratando de resolver el problema lo antes posible y una resolución debería aplicarse lo antes posible. Según nuestras observaciones, los fracasos son intermitentes, por lo que cualquier operación de empuje o de empuje que no tenga éxito como se espera puede ser retrigado. Tan pronto como tengamos confianza en que se ha implementado una solución, actualizaremos la página de estado para reflejar esto.

6. July 28, 2026 at 3:56 PM UTCresolved

   El incidente ya se ha resuelto, la vigilancia continua ha demostrado que la plataforma ha vuelto a la estabilidad normal. Todos los usuarios previamente afectados deben ser capaces de empujar y extraer datos de y a Xero como se espera. Si sigues afectado por este problema, contacta con [email protected]

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 12:06 PM UTCinvestigating

   Estamos investigando activamente un problema que impide que un subconjunto de usuarios vincule sus empresas Xero a Codat. Los usuarios afectados notarán que al ser redirigido a Xero durante el flujo de enlace, aparecerá una página de error Xero, con un código de error de 500. Este incidente se actualizará tan pronto como hayamos identificado el problema, y a más tardar las 14:05

2. July 17, 2026 at 12:07 PM UTCinvestigating

   Hemos identificado una mitigación mientras seguimos investigando la causa raíz. Los usuarios deben ahora ser capaces de vincular las empresas Xero a Codat. Este incidente se actualizará tan pronto como hayamos probado y lanzado una solución permanente.

3. July 17, 2026 at 12:07 PM UTCidentified

   Hemos identificado una mitigación mientras seguimos investigando la causa raíz. Los usuarios deben ahora ser capaces de vincular las empresas Xero a Codat. Este incidente se actualizará tan pronto como hayamos probado y lanzado una solución permanente.

4. July 17, 2026 at 3:01 PM UTCresolved

   El incidente ya se ha resuelto, la vigilancia continua ha demostrado que la plataforma ha vuelto a la estabilidad normal. Todos los usuarios previamente afectados deberían poder conectar sus Xero Companies a Codat. Si sigues afectado por este problema, contacta con [email protected]

Traducido automáticamente desde la actualización oficial del incidente.

1. June 22, 2026 at 3:22 PM 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. June 22, 2026 at 3:43 PM 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. June 22, 2026 at 6:25 PM 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. June 2, 2026 at 2:01 PM 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. June 2, 2026 at 2:07 PM 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. June 2, 2026 at 2:45 PM 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. May 29, 2026 at 2:03 PM 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. May 29, 2026 at 2:07 PM 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. May 29, 2026 at 2:50 PM UTCresolved

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

1. May 29, 2026 at 11:17 AM 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. June 3, 2026 at 2:42 PM 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. April 21, 2026 at 3:59 PM 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. April 21, 2026 at 4:02 PM UTCinvestigating

   We are continuing to investigate this issue.

3. April 21, 2026 at 5:41 PM UTCidentified

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

4. April 21, 2026 at 6:51 PM 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. April 22, 2026 at 12:24 PM 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. March 26, 2026 at 10:47 AM 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. March 26, 2026 at 11:21 AM 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. March 26, 2026 at 3:23 PM 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. March 19, 2026 at 12:49 PM 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. March 19, 2026 at 1:09 PM 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. March 19, 2026 at 1:22 PM 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. March 13, 2026 at 2:12 PM 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. March 13, 2026 at 10:05 AM 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. March 6, 2026 at 10:26 AM 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. March 6, 2026 at 10:38 AM 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. March 6, 2026 at 2:53 PM 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. February 24, 2026 at 10:34 AM 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. February 24, 2026 at 10:38 AM UTCinvestigating

   We are continuing to investigate this issue.

3. February 24, 2026 at 11:10 AM 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. February 24, 2026 at 2:59 PM 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]