Changes / Census / LinkedIn Sync Failures - server responding with status 426
Census: Major incident: LinkedIn Sync Failures - server responding with status 426
Summary
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 diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: LinkedIn Sync Failures - server responding with status 426
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-16 11:42 UTC
Before: not present
After: 2026-09-16 15:33 UTC
Before: not present
After: Census Sync Management UI
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: LinkedIn Sync Failures - server responding with status 426 (this change) 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. | Major incident |