- Level
- confirmed
- Worst impact
- Degraded
- Components
- Sync Engine
- Down Index
- 23of 100
What to do
Check whether you use Census Sync Engine. 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 27m it lasted.
Anything that failed between 2024-11-15 04:06 UTC and 2024-11-15 04: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 4
- investigating
Syncs are completing at slower than usual rates and we are investigating the issue
provider
- identified
We have identified stuck sync workers and we are replacing these containers with new capacity
provider
- monitoring
We have rolled back a feature that we believe caused the slowdown and added extra capacity to compensate for the slowdown. Sync completion rates have returned to normal levels and any slowdown or queueing should be resolved in the next 30 minutes.
provider
- resolved
This incident has been resolved.
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-7b59327f14
Is Census still down?
No, this incident was resolved 2024-11-15 04:33 UTC. For Census's live state, see https://down.guide/census.
How long did it last?
27m, from 2024-11-15 04:06 UTC to 2024-11-15 04:33 UTC, by the times Census posted.
What was affected?
Census named Sync Engine.
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.