Companies / Census / incidents
Census: LinkedIn Sync Failures - server responding with status 426
Census reported a major incident affecting some customers: LinkedIn syncs failed with status 426, and new and existing LinkedIn Destination tests could fail. It started at 2026-09-16 11:42 UTC and was resolved at 2026-09-16 15:33 UTC, lasting 3 h 50 min. Impacted syncs should recover on their next scheduled or manual run; destination connections and tests should work again.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Census Sync Management UI
Timeline of updates
- 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.
- 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.
Rewindex changes for this incident
- Major incident: LinkedIn Sync Failures - server responding with status 426 2026-09-16 11:42 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Census profile · Recent Census incidents · Markdown · JSON