Outage in Census
LinkedIn Sync Failures - server responding with status 426
Resolved MajorIncident Report
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.
Components affected
Census Sync Management UITrusted by 1,000+ teams
The Status Page Aggregator with Early Outage Detection
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
17 days ago - at 09/16/2026 03:33PM
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
17 days ago - at 09/16/2026 12:42PM
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.
Latest Census outages
App failing to load - 24 days ago
Degraded UI performance - 24 days ago
Facebook (Meta) Sync Failures - API access disrupted - about 1 month ago
Service incident impacting app and sync execution - 3 months ago
Census Web Outage - 7 months ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
