DataBlend Concur Issue

4/17/26 4:40 PM ET Update

Thank you for your patience while we resolved the Concur connection issue. We worked closely with Concur and its third-party vendor, Akamai, and the issue has now been fully resolved.

Your workflows should run normally again; however, please validate your results for this week and reach out to DataBlend Support if you have any questions or concerns.

If you need assistance, please contact us at support@datablend.com. 

4/16/26 9:00 AM ET Update

We’ve confirmed that the Concur disruption is due to a connectivity issue with Akamai, an infrastructure provider for Concur, which has been preventing certain requests from being processed as expected.

Our team has shared supporting evidence to help facilitate a resolution and is actively following up with both Concur and Akamai. We’re treating this as a top priority and will continue to provide updates as more information becomes available. 

If you have any questions or need assistance, please contact our Support team at support@datablend.com.  

4/15/26 Issue

We want to make you aware of a current issue impacting multiple Concur groups. Our product team is actively investigating the issue. Based on our initial review, it appears this behavior may have started at 9PM ET on Monday.

While some Concur collectors and targets are still running, the majority of core objects are returning this error. As we work toward a resolution, we recommend reviewing your permission and credential settings to ensure everything is configured correctly.

We’ll share another update as soon as we have more information. We appreciate your patience and apologize for the disruption this may cause.

If you have any questions or need assistance, please contact our Support team at support@datablend.com.