Codat driftsforstyrrelser

1. 24. august 2026 kl. 13.49 UTCidentified

   Vi er klar over et problem, der påvirker en række af vores integrations og sync-tjenester og er i øjeblikket at gennemføre en rettelse til at opklare problemet. Anmodninger til disse tjenester returnerer i øjeblikket fejl. Genforsøg vil returnere den samme fejl, indtil vi har rettet problemet, så ingen handling er nødvendig fra dig. Queued syncs vil fortsætte automatisk, når tjenesten er genoprettet. Alle andre integreringer og tjenester fungerer normalt. Vi opdaterer denne side, så snart vi har mere at dele. Denne hændelse vil blive opdateret, så snart vi har testet og rullet ud en rettelse, og senest 4: 00PM GMT.

2. 24. august 2026 kl. 14.36 UTCmonitoring

   Vi har implementeret et fix. Berørte brugere bør nu bemærke, at de igen er i stand til at bruge de berørte tjenester som normalt. I kø vil synkerne fortsætte automatisk. Vores hold fortsætter med at overvåge platformen for at sikre fortsat stabilitet. Hvis du oplever problemer, bedes du kontakte support @ codat.io for yderligere hjælp.

3. 24. august 2026 kl. 15.46 UTCresolved

   Hændelsen er nu blevet løst, løbende overvågning har vist, at platformen er vendt tilbage til normal stabilitet. Alle brugere, der tidligere har været berørt, bør kunne benytte de berørte tjenester uden afbrydelse. Hvis du stadig er påvirket af dette spørgsmål, bedes du kontakte support @ codat.io

Automatisk oversat fra den officielle hændelsesopdatering.

1. 11. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. juli 2026 kl. 15.08 UTCinvestigating

   Vi undersøger aktivt et problem, der forhindrer brugerne i både at bruge Codat-portalen og kalde vores offentlige front API 'er. Berørte brugere vil bemærke, at de ikke er i stand til at ringe til Codat Api uden en fejl eller login til Codat portal. Denne hændelse vil blive opdateret, så snart vi har identificeret problemet, og senest 17: 07

2. 27. juli 2026 kl. 15.09 UTCmonitoring

   Vi har implementeret et fix til det totale udfald. Berørte brugere bør nu bemærke, at de igen er i stand til at bruge Codat portal og Api som normalt. Vores hold fortsætter med at overvåge platformen for at sikre fortsat stabilitet. Hvis du oplever problemer, bedes du kontakte support @ codat.io for yderligere hjælp.

3. 27. juli 2026 kl. 18.33 UTCresolved

   Hændelsen er nu blevet løst, som løbende overvågning har vist platformen er vendt tilbage til normal stabilitet. Du kan have bemærket fejl med Codat API eller Codat Portal fra 14: 54-15: 06 UTC Hvis du stadig er påvirket af dette spørgsmål, bedes du kontakte support @ codat.io

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 12.43 UTCinvestigating

   Vi undersøger aktivt et problem, der forhindrer brugerne i at logge ind på Codat Portal og gøre API opkald til vores offentlige API. Berørte brugere vil bemærke, at de ikke er i stand til at logge ind på Codat webportal og foretage API-opkald. Der ville være en 500 kategori fejl i begge tilfælde. Denne hændelse vil blive opdateret, så snart vi har identificeret problemet, og senest 14: 40

2. 24. juli 2026 kl. 12.48 UTCmonitoring

   Vi har implementeret et fix for udbruddet. Codats tjenester og Portal bør nu være tilgængelige igen. Vores hold fortsætter med at overvåge platformen for at sikre fortsat stabilitet. Hvis du oplever problemer, bedes du kontakte support @ codat.io for yderligere hjælp.

3. 24. juli 2026 kl. 12.57 UTCresolved

   Hændelsen er nu blevet løst, løbende overvågning har vist, at platformen er vendt tilbage til normal stabilitet. Hvis du stadig er påvirket af dette spørgsmål, bedes du kontakte support @ codat.io

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juli 2026 kl. 14.11 UTCinvestigating

   Vi undersøger aktivt et problem, der forhindrer brugerne i at bruge Pulling og Pushing Data til Xero. Berørte brugere vil bemærke, at alle Xero Push and Pull Operations resulterer i en fejl. Denne hændelse vil blive opdateret, så snart vi har identificeret problemet, og senest 16: 09

2. 22. juli 2026 kl. 14.34 UTCmonitoring

   Push and Pull For Xero integration fungerer nu igen som forventet. Vores hold fortsætter med at overvåge platformen for at sikre fortsat stabilitet. Hvis du oplever problemer, bedes du kontakte support @ codat.io for yderligere hjælp.

3. 22. juli 2026 kl. 15.37 UTCresolved

   Denne hændelse er nu løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 09.55 UTCinvestigating

   Efter hændelsen https: / / status.codat.io / hændelser / 92vdwfbdrw97 observerer vi stadig nogle Xero-fejl. Berørte brugere vil bemærke, at deres push eller pull operationer til Xero mislykkes med en Auth - relateret fejl. Fejlene synes at være forbigående, så vores brugere rådes til at prøve alle mislykkede operationer igen.

2. 24. juli 2026 kl. 10.48 UTCinvestigating

   Vi har identificeret årsagen til hændelsen og er i øjeblikket ved at gennemføre en rettelse for at opklare problemet. Denne hændelse vil blive opdateret, så snart vi har testet og rullet ud en rettelse og senest 12: 48 UK Time

3. 24. juli 2026 kl. 11.25 UTCinvestigating

   Vi har identificeret årsagen til hændelsen og er i øjeblikket ved at gennemføre en rettelse for at opklare problemet. Denne hændelse vil blive opdateret, så snart vi med succes har testet og rullet ud fix, som vil være senest 13: 25

4. 28. juli 2026 kl. 08.13 UTCidentified

   Vi arbejder fortsat sammen med vores partnere i Xero i et forsøg på at mindske dette problem. Som i vores observationer, fejlene er intermitterende, så ethvert skub eller træk operationer, der ikke lykkes som forventet kan genprøves. Så snart vi er sikre på, at en rettelse er blevet indsat, vil vi opdatere statussiden for at afspejle dette.

5. 28. juli 2026 kl. 09.55 UTCidentified

   Vi fortsætter med at arbejde sammen med vores partner Xero, og der er blevet identificeret en beslutning. Begge parter søger at løse problemet som et ap, og en beslutning bør gennemføres så hurtigt som muligt. Som i vores observationer, fejlene er intermitterende, så ethvert skub eller træk operationer, der ikke lykkes som forventet kan genprøves. Så snart vi er sikre på, at en rettelse er blevet indsat, vil vi opdatere statussiden for at afspejle dette.

6. 28. juli 2026 kl. 15.56 UTCresolved

   Hændelsen er nu blevet løst, løbende overvågning har vist, at platformen er vendt tilbage til normal stabilitet. Alle brugere, der tidligere har været berørt, bør kunne skubbe og trække data fra og til Xero som forventet. Hvis du stadig er påvirket af dette spørgsmål, bedes du kontakte support @ codat.io

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. juli 2026 kl. 12.06 UTCinvestigating

   Vi undersøger aktivt et problem, der forhindrer en undergruppe af brugere i at forbinde deres Xero-virksomheder til Codat. Berørte brugere vil bemærke, at når de omdirigeres til Xero under linket flow, vil en Xero fejl side vise, med en 500 fejlkode. Denne hændelse vil blive opdateret, så snart vi har identificeret problemet, og senest 14: 05

2. 17. juli 2026 kl. 12.07 UTCinvestigating

   Vi har identificeret en afbødning, mens vi fortsætter med at undersøge den grundlæggende årsag. Brugerne bør nu være i stand til at forbinde Xero virksomheder til Codat. Denne hændelse vil blive opdateret, så snart vi har testet og rullet ud en permanent rettelse.

3. 17. juli 2026 kl. 12.07 UTCidentified

   Vi har identificeret en afbødning, mens vi fortsætter med at undersøge den grundlæggende årsag. Brugerne bør nu være i stand til at forbinde Xero virksomheder til Codat. Denne hændelse vil blive opdateret, så snart vi har testet og rullet ud en permanent rettelse.

4. 17. juli 2026 kl. 15.01 UTCresolved

   Hændelsen er nu blevet løst, løbende overvågning har vist, at platformen er vendt tilbage til normal stabilitet. Alle tidligere berørte brugere bør nu igen være i stand til at forbinde deres Xero Companies til Codat. Hvis du stadig er påvirket af dette spørgsmål, bedes du kontakte support @ codat.io

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 14.50 UTCresolved

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

1. 29. maj 2026 kl. 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. juni 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 16.02 UTCinvestigating

   We are continuing to investigate this issue.

3. 21. april 2026 kl. 17.41 UTCidentified

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

4. 21. april 2026 kl. 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. april 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 10.38 UTCinvestigating

   We are continuing to investigate this issue.

3. 24. februar 2026 kl. 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. februar 2026 kl. 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]