Skip to main content
Census

Degraded sync performance

Degraded Lasted 13m · started · Census's page

Level
confirmed
Worst impact
Degraded
Components
Sync Engine
Regions
us
Down Index
21of 100

What to do

  • Check whether you use Census Sync Engine in us. 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 13m it lasted.

    Anything that failed between 2025-01-30 21:44 UTC and 2025-01-30 21:57 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

  1. investigating

    Our monitoring has notified us that some syncs are performing more slowly than usual - we are investigating

    provider

  2. 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-36605d5af1

Is Census still down?

No, this incident was resolved 2025-01-30 21:57 UTC. For Census's live state, see https://down.guide/census.

How long did it last?

13m, from 2025-01-30 21:44 UTC to 2025-01-30 21:57 UTC, by the times Census posted.

What was affected?

Census named Sync Engine in us.

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.