Is Codat down?
Last checked just nowNo incidents right now.
Codat is operational right now. Last checked just now; the most recent incident resolved 16d ago.
Real-time Codat status, recent outages, and incident history — pulled directly from Codat's official status page at https://status.codat.io every 5 minutes. Pingoru tracks 174 Codat services and has captured 7 incidents in the last 90 days (99.86% uptime). Get email, Slack, Discord, or webhook alerts the moment Codat reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- resolved · Jun 03, 2026, 02:42 PM UTC
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.
Latest: 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 ha…
-
- API Connectivity
Timeline · 3 updates
- identified · Jun 02, 2026, 02:01 PM UTC
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.
- monitoring · Jun 02, 2026, 02:07 PM UTC
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.
- resolved · Jun 02, 2026, 02:45 PM UTC
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]
Latest: 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 wit…
-
- Sync For Expenses ConnectivityDynamics 365 Business CentralOracle NetSuiteQuickBooks DesktopQuickBooks OnlineXeroSage IntacctZoho BooksQuickBooks DesktopQuickBooks Desktop
Timeline · 3 updates
- investigating · May 29, 2026, 02:03 PM UTC
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
- monitoring · May 29, 2026, 02:07 PM UTC
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.
- resolved · May 29, 2026, 02:50 PM UTC
This incident has been resolved. Pushing to QBD is now working as expected.
Latest: This incident has been resolved. Pushing to QBD is now working as expected.
-
-
Timeline · 1 update
- resolved · May 29, 2026, 11:17 AM UTC
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. 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 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.
Latest: 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 authenticati…
-
- QuickBooks DesktopQuickBooks DesktopQuickBooks Desktop
Timeline · 5 updates
- investigating · Apr 21, 2026, 03:59 PM UTC
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
- investigating · Apr 21, 2026, 04:02 PM UTC
We are continuing to investigate this issue.
- identified · Apr 21, 2026, 05:41 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Apr 21, 2026, 06:51 PM UTC
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.
- resolved · Apr 22, 2026, 12:24 PM UTC
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]
Latest: 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 complet…
-
See the full Codat outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Codat outage history →Or sign up free to get alerts when Codat breaks · 10 free monitors · No credit card
- Started Jun 03, 2026, 02:42 PM UTC · Resolved May 28, 2026, 03:30 PM UTC · —
- Started Jun 02, 2026, 02:01 PM UTC · Resolved Jun 02, 2026, 02:45 PM UTC · 43m
- Started May 29, 2026, 02:03 PM UTC · Resolved May 29, 2026, 02:50 PM UTC · 47m
- Started May 29, 2026, 11:17 AM UTC · Resolved May 29, 2026, 11:17 AM UTC · —
- Started Apr 21, 2026, 03:59 PM UTC · Resolved Apr 22, 2026, 12:24 PM UTC · 20h 25m
- Dataset delay in processing stage ResolvedStarted Mar 26, 2026, 10:47 AM UTC · Resolved Mar 26, 2026, 03:23 PM UTC · 4h 36m
- Started Mar 19, 2026, 12:49 PM UTC · Resolved Mar 19, 2026, 01:22 PM UTC · 33m