- Detected by Pingoru
- Oct 09, 2025, 08:59 AM UTC
- Resolved
- Oct 09, 2025, 09:48 AM UTC
- Duration
- 48m
Affected: Portal
Timeline · 3 updates
-
investigating Oct 09, 2025, 08:59 AM UTC
We are actively investigating an issue preventing users from viewing a Company's data in the portal. Affected users will notice that an error will show when they attempt to view a company's data in the portal This incident will be updated as soon as we have identified the issue, and no later than 10:59
-
monitoring Oct 09, 2025, 09:28 AM UTC
We have implemented a fix and now the data pages in the portal should be viewable. Affected users may need to clear their browser cache and cookies. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact [email protected] for further assistance.
-
resolved Oct 09, 2025, 09:48 AM 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 view the Data of their Companies in the Codat portal. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Oct 03, 2025, 12:02 PM UTC
- Resolved
- Oct 03, 2025, 03:37 PM UTC
- Duration
- 3h 34m
Affected: ClearbooksAmazon Seller CentralLending ConnectivitySync For Expenses ConnectivitySync For Commerce ConnectivityBill Pay (Sync) ConnectivitySync For Payroll ConnectivitySpend Insights ConnectivityBill Pay (async) ConnectivityPlaidDynamics 365 Business CentralBig CommerceExactTrueLayerCloverFreeAgentLightspeed Restaurant (Series K)FreshbooksMolliePayPalMYOBPrestaShopOracle NetSuiteShopifySquareQuickBooks DesktopSumUpQuickBooks OnlineStripeSage 200cloudWooCommerceSage 50ZettleSage Business Cloud AccountingSage IntacctXeroWaveZoho Books
Timeline · 3 updates
-
investigating Oct 03, 2025, 12:02 PM UTC
We are actively investigating an issue whereby any data operations in Codat, (Push and Pull), are completing much more slowly than expected. This incident will be updated as soon as we have identified the issue, and no later than 14:00
-
monitoring Oct 03, 2025, 12:42 PM UTC
We have implemented a fix and believe that normal service has been resumed. Affected users should now notice that Push and Pull operations in Codat are completing within the expected timeframe Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact [email protected] for further assistance.
-
resolved Oct 03, 2025, 03:37 PM UTC
The incident has now been resolved, the root cause of the problem was an underlying issue with our 3rd party Cloud Services provider and has been escalated appropriately on their side. Ongoing monitoring has shown that the mitigations we have put in place, returned our platform to normal stability. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2025, 04:05 PM UTC
- Resolved
- Oct 03, 2025, 08:54 AM UTC
- Duration
- 16h 49m
Affected: Xero Bank FeedsXeroXeroXeroXeroXero
Timeline · 3 updates
-
investigating Oct 02, 2025, 04:05 PM UTC
We are actively investigating an issue whereby Xero Push operations are completing much slower than usual. Affected users will notice that push operations to Xero may take a long period of time rather than a few seconds. This incident will be updated as soon as we have identified the issue.
-
monitoring Oct 02, 2025, 08:57 PM UTC
We have implemented a fix in production. Affected users should now notice that push operations to Xero are processing 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 Oct 03, 2025, 08:54 AM UTC
The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All push operations to the Xero Accounting system should now complete within a few minutes, as they ordinarily do. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2025, 03:52 PM UTC
- Resolved
- Oct 01, 2025, 05:10 PM UTC
- Duration
- 1h 18m
Affected: Sage IntacctSage IntacctSage IntacctSage IntacctSage Intacct
Timeline · 2 updates
-
investigating Oct 01, 2025, 03:52 PM UTC
We are actively investigating an issue whereby Sage Intacct Bills datasets are very intermittently missing their line items. Affected users may notice that line items return after certain data syncs. This incident will be updated as soon as we have identified the root cause of the issue.
-
resolved Oct 01, 2025, 05:10 PM UTC
The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should no longer notice missing line items following completion of Sage Intacct Bills datasets. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Sep 26, 2025, 12:56 PM UTC
- Resolved
- Sep 26, 2025, 03:09 PM UTC
- Duration
- 2h 13m
Affected: Shopify
Timeline · 3 updates
-
investigating Sep 26, 2025, 12:56 PM UTC
We are actively investigating an issue which is affecting datasets from Shopify connections. Affected users will notice that some commerce datasets are failing with a FetchError.
-
investigating Sep 26, 2025, 02:10 PM UTC
We have identified the cause of the incident and are currently implementing a fix to remediate. This incident will be updated as soon as we have successfully tested and rolled out a fix.
-
resolved Sep 26, 2025, 03:09 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 fetch data from a Shopify connection without disruption. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Aug 22, 2025, 11:00 AM UTC
- Resolved
- Sep 04, 2025, 03:22 AM UTC
- Duration
- 12d 16h
Affected: QuickBooks DesktopQuickBooks DesktopQuickBooks DesktopQuickBooks DesktopQuickBooks Desktop
Timeline · 4 updates
-
investigating Aug 25, 2025, 06:51 PM UTC
We are actively investigating an issue which is intermittently affecting datasets from QuickBooks Desktop companies. Affected users will notice that some datasets fail with a FetchError. This is usually when the dataset is slightly larger in size than average.
-
investigating Aug 27, 2025, 03:37 PM UTC
We are still actively investigating this issue. Affected clients will notice that their QuickBooks Desktop connections are unable to complete a read sync (pull operation) in Production for some datasets. Datasets affected will typically return a status of 'fetchError'. While we are still looking into this issue, as a partial workaround, we recommend clients to reduce the range of data synced for affected connections. Please contact [email protected] for further assistance on reducing the range of the data synced for your affected connections.
-
monitoring Aug 27, 2025, 06:16 PM UTC
We have implemented a fix. Affected users should notice that Quickbooks Desktop syncs have returned to 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 Sep 04, 2025, 03:22 AM UTC
The incident has now been resolved, ongoing monitoring has shown the Quickbooks Desktop platform has returned to normal stability. All users previously affected should be able to pull data without disruption. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2025, 08:33 AM UTC
- Resolved
- Aug 21, 2025, 07:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 21, 2025, 08:33 AM UTC
Our monitoring flagged that a small percentage of requests failed with 5XX status codes or timeouts between 8:02BST and 08:32BST. The cause of the issue has been identified as a traffic being directed to a bad application instance. Service has now been restored. If you are still affected by this issue, please contact [email protected] for further assistance.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2025, 03:59 PM UTC
- Resolved
- Aug 14, 2025, 02:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 14, 2025, 03:59 PM UTC
Our monitoring flagged that a small minority of QuickBooks Desktop fetch operations may have completed more slowly than expected. An even smaller subset of these eventually moved into a FetchError state. We have now fully restored this functionality. Consumers of the Codat system should be able to requeue all QBD datasets and expect them to complete as expected. The incident began at approximately 15:13 UK time and was fully assuaged by 16:35. If you are still affected by this issue, please contact [email protected] for further assistance.
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2025, 11:04 AM UTC
- Resolved
- Jul 29, 2025, 12:17 PM UTC
- Duration
- 1h 12m
Affected: Lending ConnectivitySync For Expenses ConnectivitySync For Commerce ConnectivityBank Feeds ConnectivityBill Pay (Sync) ConnectivitySync For Payroll ConnectivitySpend Insights ConnectivityBill Pay (async) Connectivity
Timeline · 3 updates
-
identified Jul 29, 2025, 11:04 AM UTC
We have identified an issue causing an delay in processing datasets are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix in production, and no later than 13:00 BST.
-
monitoring Jul 29, 2025, 11:09 AM UTC
We have implemented a fix in production. Affected users should now notice that datasets are processing 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 Jul 29, 2025, 12:17 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 sync data without disruption. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2025, 03:50 PM UTC
- Resolved
- Jul 14, 2025, 03:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 14, 2025, 03:50 PM UTC
Our monitoring flagged that the Codat Portal and API were down between 16:34 and 16:41 UK time. Affected users would have noticed that accessing the Codat Portal or calling the Codat API returned intermittently 500s and 404s error codes. The cause of the issue has been identified as a temporary unavailability of our servers. We rolled back and redeployed our hosted apps and the service was restored successfully. If you are still affected by this issue, please contact [email protected] for further assistance.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2025, 04:39 PM UTC
- Resolved
- Jul 02, 2025, 07:39 PM UTC
- Duration
- 3h
Affected: Link
Timeline · 3 updates
-
investigating Jul 02, 2025, 04:39 PM UTC
We are currently investigating an issue with the Link URL when using the Portal. You may be experiencing a "Parsing Error" when accessing the URL
-
monitoring Jul 02, 2025, 04:48 PM UTC
We have implemented a fix. Affected users should notice that the Link URL and Linking flow has returned to 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 Jul 02, 2025, 07:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2025, 03:14 PM UTC
- Resolved
- Jun 27, 2025, 04:13 PM UTC
- Duration
- 59m
Affected: Lending ConnectivitySync For Expenses ConnectivitySync For Commerce ConnectivityBank Feeds ConnectivityBill Pay (Sync) ConnectivitySync For Payroll ConnectivitySpend Insights ConnectivityBill Pay (async) Connectivity
Timeline · 3 updates
-
investigating Jun 27, 2025, 03:14 PM UTC
We are actively investigating an issue causing Internal errors on datasets during validation. Affected users will notice that datasets may fail with a Internal error. This incident will be updated as soon as we have identified the issue, and no later than 5:00 BST.
-
monitoring Jun 27, 2025, 03:21 PM UTC
We have implemented a fix in production. Affected users should now notice that datasets are no longer failing with Internal Errors. 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 27, 2025, 04:13 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 sync datasets without disruption and we have requeued any datasets that failed with InternalErrors previously. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2025, 09:32 AM UTC
- Resolved
- Jun 26, 2025, 03:40 PM UTC
- Duration
- 6h 8m
Affected: FreeAgentFreeAgentFreeAgent
Timeline · 4 updates
-
investigating Jun 26, 2025, 09:32 AM UTC
We are actively investigating an issue preventing users from attaching files to expenses and bills for FreeAgent companies. Affected users will notice that they are getting a 'Platform Error' message when attempting to post an attachment to an expense or a bill to a FreeAgent company. This incident will be updated as soon as we have identified the issue, and no later than 12pm.
-
investigating Jun 26, 2025, 11:01 AM UTC
We are still investigating this issue and evaluating our lead hypotheses. This incident will be updated as soon as possible and before 2:30pm UK time latest.
-
monitoring Jun 26, 2025, 01:00 PM UTC
We have implemented a fix in Production. Affected users should now notice that they are able to attach files to expenses and bills for FreeAgent companies. 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 26, 2025, 03:40 PM UTC
The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. The cause of the issue has been identified as code released by a third-party and resulting in an error. The affected third-party code has been rolledback successfully. All users previously affected should be able to attach files to bills and expenses in their FreeAgent companies without disruption. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2025, 04:44 PM UTC
- Resolved
- Jun 25, 2025, 05:56 PM UTC
- Duration
- 1h 12m
Affected: Spend Insights Connectivity
Timeline · 3 updates
-
investigating Jun 25, 2025, 04:44 PM UTC
We are currently investigating an issue that is affecting the report generation within Codat's Spend Insights product. You may notice that generating and downloading a "Spend Analysis" report is failing.
-
monitoring Jun 25, 2025, 05:21 PM UTC
We have implemented a fix. Affected users should notice that Spend Insights report generation has returned to 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 25, 2025, 05:56 PM UTC
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]
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2025, 09:43 AM UTC
- Resolved
- Jun 18, 2025, 03:54 PM UTC
- Duration
- 6h 10m
Affected: API ConnectivityPortal
Timeline · 3 updates
-
investigating Jun 18, 2025, 09:43 AM UTC
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 incident will be updated as soon as we have identified the issue, and no later than 11:45am.
-
monitoring Jun 18, 2025, 10:11 AM UTC
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.
-
resolved Jun 18, 2025, 03:54 PM UTC
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]
Read the full incident report →
- Detected by Pingoru
- Jun 13, 2025, 07:48 PM UTC
- Resolved
- Jun 13, 2025, 08:39 PM UTC
- Duration
- 50m
Affected: API ConnectivityLending ConnectivitySync For Expenses ConnectivitySync For Commerce ConnectivityBank Feeds ConnectivityBill Pay (Sync) ConnectivitySync For Payroll ConnectivitySpend Insights ConnectivityBill Pay (async) Connectivity
Timeline · 3 updates
-
investigating Jun 13, 2025, 07:48 PM UTC
We are actively investigating an issue causing datasets to be stuck in the ValidationQueued state. This incident will be updated as soon as we have identified the issue, and no later than 21:45 BST.
-
monitoring Jun 13, 2025, 07:56 PM UTC
We have implemented a fix in production. Affected users should now notice that datasets begin 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.
-
resolved Jun 13, 2025, 08:39 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 sync datasets without disruption. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- May 21, 2025, 05:44 PM UTC
- Resolved
- May 21, 2025, 07:13 PM UTC
- Duration
- 1h 29m
Affected: QuickBooks Online Bank FeedsQuickBooks OnlineQuickBooks OnlineQuickBooks OnlineQuickBooks OnlineQuickBooks OnlineQuickBooks OnlineQuickBooks OnlineQuickBooks Online
Timeline · 3 updates
-
investigating May 21, 2025, 05:44 PM UTC
We are actively investigating an issue preventing some users from successfully pushing data to QBO . Affected users will notice that pushes are sitting in a pending state for a long time before completing successfully.
-
monitoring May 21, 2025, 06:42 PM UTC
Affected users should now notice that push requests to QBO process in a timely manner. 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 21, 2025, 07:13 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 push new data via the Codat API for their QBO companies without disruption. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- May 21, 2025, 02:27 PM UTC
- Resolved
- May 21, 2025, 02:27 PM UTC
- Duration
- —
Affected: API ConnectivityLending ConnectivitySync For Expenses ConnectivitySync For Commerce ConnectivityBank Feeds ConnectivityBill Pay (Sync) ConnectivitySync For Payroll Connectivity
Timeline · 1 update
-
resolved May 21, 2025, 02:27 PM UTC
Our monitoring flagged an issue with our API intermittently timing out between 02:16 UTC and 02:28 UTC. Affected users may have noticed that their API calls were yielding 504 error codes. The cause of the issue has been identified as an issue with our cloud infrastructure provider. Service has now been restored and we are working with the third party to ensure there are no further regressions. If you are still affected by this issue, please contact [email protected] for further assistance.
Read the full incident report →
- Detected by Pingoru
- May 20, 2025, 03:47 PM UTC
- Resolved
- May 20, 2025, 04:00 PM UTC
- Duration
- 12m
Affected: API ConnectivityLending ConnectivitySync For Expenses ConnectivitySync For Commerce ConnectivityBank Feeds ConnectivityBill Pay (Sync) ConnectivitySync For Payroll ConnectivitySpend Insights Connectivity
Timeline · 3 updates
-
investigating May 20, 2025, 03:47 PM UTC
We are actively investigating an issue which is causing intermittent timeouts for our API Affected users may notice that certain API calls are timing out or taking longer than usual to complete. This incident will be updated as soon as we have identified the issue, and no later than 17:45
-
monitoring May 20, 2025, 03:55 PM UTC
We have implemented a fix here. Affected users should now notice that the response times of our API have returned to 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 May 20, 2025, 04:00 PM UTC
The incident has now been resolved as ongoing monitoring has shown the platform has returned to normal stability. API responses should have now returned to being performant. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- May 13, 2025, 04:16 PM UTC
- Resolved
- May 14, 2025, 04:35 PM UTC
- Duration
- 1d
Affected: Link
Timeline · 4 updates
-
investigating May 13, 2025, 04:16 PM UTC
Our monitoring flagged that intermittent errors started occurring in the link flow on 1:20PM GMT on 12th May. Affected users may have noticed a "Something went wrong" error message occurred when attempting to link a company, preventing completion of the link flow.
-
identified May 13, 2025, 04:33 PM UTC
The cause of the issue has been identified and a fix is being implemented.
-
monitoring May 13, 2025, 05:24 PM UTC
A fix was implemented at 5:30PM GMT and we are monitoring the results. If you are still affected by this issue, please contact [email protected] for further assistance.
-
resolved May 14, 2025, 04:35 PM UTC
This incident has now been resolved. Link Flow has been fully restored. If you are still affected by this issue, please contact [email protected] for further assistance.
Read the full incident report →
- Detected by Pingoru
- May 12, 2025, 10:58 AM UTC
- Resolved
- May 12, 2025, 05:14 PM UTC
- Duration
- 6h 15m
Affected: Sage 50Sage 50
Timeline · 6 updates
-
investigating May 12, 2025, 10:58 AM UTC
We are actively investigating an issue preventing Sage 50 connected companies from fetching data. Sage50 connected companies should notice that all datasets fail with a FetchError This incident will be updated as soon as we have identified the issue, and no later than 12:57
-
identified May 12, 2025, 11:23 AM UTC
We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix, and no later than 13:30
-
investigating May 12, 2025, 12:21 PM UTC
We have identified the cause of the incident and are continuing to implement a fix.
-
identified May 12, 2025, 12:21 PM UTC
We have identified the cause of the incident and are continuing to implement a fix.
-
monitoring May 12, 2025, 02:20 PM UTC
We have implemented a fix to the problems we had been experiencing with our Sage50 integration. Affected users should now notice that there fetch operations for Sage50 are able to complete without error. 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 12, 2025, 05:14 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 fetch data from Sage 50 without error. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- May 09, 2025, 01:35 PM UTC
- Resolved
- May 09, 2025, 02:34 PM UTC
- Duration
- 59m
Affected: API ConnectivityPortal
Timeline · 3 updates
-
investigating May 09, 2025, 01:35 PM UTC
We are actively investigating an issue resulting in timeouts in the portal and making API requests. Affected users will notice that some requests are timing out resulting in intermittent page loading and failed requests. This incident will be updated as soon as we have identified the issue, and no later than 15.30 BST.
-
monitoring May 09, 2025, 01:43 PM UTC
We are no longer seeing the timeouts in production and affected users should not experience further requests timing out or the portal failing to load. 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 09, 2025, 02:34 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 make requests to the API and use the portal without disruption. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- May 06, 2025, 02:21 PM UTC
- Resolved
- May 06, 2025, 02:21 PM UTC
- Duration
- —
Affected: Portal
Timeline · 1 update
-
resolved May 06, 2025, 02:21 PM UTC
Our monitoring alerted us to the fact that between 11:48 and 12:01 GMT, some logins to the Codat portal may have been failing with an error. The cause of the issue has been identified as an problem with our cloud infrastructure provider, which has now been resolved. If you are still affected by this issue, please contact [email protected] for further assistance.
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2025, 07:47 AM UTC
- Resolved
- Apr 25, 2025, 01:04 PM UTC
- Duration
- 5h 17m
Affected: Oracle NetSuiteOracle NetSuiteOracle NetSuiteOracle NetSuiteOracle NetSuiteOracle NetSuite
Timeline · 4 updates
-
investigating Apr 25, 2025, 07:47 AM UTC
We are actively investigating an issue preventing users from syncing bills from NetSuite. Affected users will notice that any bill syncs from NetSuite will fail with a MapError. This incident will be updated as soon as we have identified the issue, and no later than 10AM BST.
-
identified Apr 25, 2025, 08:02 AM UTC
We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix, and no later than 10AM BST.
-
monitoring Apr 25, 2025, 08:16 AM UTC
We have implemented a fix in production. Affected users should now notice that NetSuite bills datasets now complete successfully. 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 25, 2025, 01:04 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 sync bills from NetSuite without disruption. If you are still affected by this issue, please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2025, 09:11 PM UTC
- Resolved
- Apr 25, 2025, 01:02 PM UTC
- Duration
- 15h 50m
Affected: API ConnectivityOracle NetSuiteOracle NetSuiteOracle NetSuiteOracle NetSuiteOracle NetSuite
Timeline · 6 updates
-
investigating Apr 24, 2025, 09:11 PM UTC
We are actively investigating an issue preventing users from pushing Bills and BillPayments to Netsuite. Affected users will notice that a 500 error response is returned. This incident will be updated as soon as we have identified the issue, and no later than 10:10 GMT
-
identified Apr 24, 2025, 09:15 PM UTC
We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix in 10:10PM GMT
-
monitoring Apr 24, 2025, 10:02 PM UTC
We have implemented a fix in Production. Affected users should now notice that Bill and BillPayment push operations no longer return a 500 response. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact [email protected] for further assistance.
-
identified Apr 25, 2025, 08:24 AM UTC
We have started seeing 500 responses again on bill and billPayments pushes to NetSuite. We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix, and no later than 10.30AM BST.
-
monitoring Apr 25, 2025, 10:44 AM UTC
We have implemented a fix in production. Affected users should now notice that they're able to push bills and billPayments to NetSuite successfully . 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 25, 2025, 01:02 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 push bills and billPayments to NetSuite without disruption. If you are still affected by this issue, please contact [email protected]
Read the full incident report →