- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Census Sync Management UI
- Down Index
- 37of 100
What to do
Check whether you use Census Census Sync Management UI. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 51m it lasted.
Anything that failed between 2026-09-16 11:42 UTC and 2026-09-16 15:33 UTC may need a replay.Subscribe to Census's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=census works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Census 2
- 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.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-43ed052d34
Is Census still down?
No, this incident was resolved 2026-09-16 15:33 UTC. For Census's live state, see https://down.guide/census.
How long did it last?
3h 51m, from 2026-09-16 11:42 UTC to 2026-09-16 15:33 UTC, by the times Census posted.
What was affected?
Census named Census Sync Management UI.
What caused it?
Census hasn't published a root cause. If it does, it shows here.
Where does this come from?
Census's official status page, https://status.getcensus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.