Census Status
LinkedIn Sync Failures - server responding with status 426

Started

Resolved

Duration

2 hrs 50 min

Resolvedmajor impactVendor link

Update timeline

Resolved

This incident has now been resolved. You should see impacted syncs recover on the next scheduled run or when triggering it manually. Connecting new LinkedIn destination or testing existing ones should now return the correct response.

Identified

Some customers are encountering an issue on LinkedIn syncs causing them to fail with the error message "server responded with status 426". Customers may also see new and existing LinkedIn Destination tests fail when testing them. The issue has been identified and the engineering team is working on a fix.

LinkedIn Sync Failures - server responding with status 426 — Census Incident Timeline & Status — DevHelm