Census incident
LinkedIn Sync Failures - server responding with status 426
Resolved after 3 hours 50 minutes, affecting Census Sync Management UI, on September 16, 2026.
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.
Affected components
Update timeline
- identified Sep 16, 2026, 12:42 PM UTC
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 Sep 16, 2026, 03:33 PM UTC
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.
Your product runs on more than Census
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services