- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 14of 100
What to do
Check whether your product depends on Census. 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 14m it lasted.
Anything that failed between 2025-07-03 01:58 UTC and 2025-07-03 02:11 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
- monitoring
There are no known problems in production but we are monitoring this AWS incident presently as it has impacted some things in our staging environment. https://health.aws.amazon.com/health/status
provider
- resolved
AWS has marked this as 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-a351c6d24d
Is Census still down?
No, this incident was resolved 2025-07-03 02:11 UTC. For Census's live state, see https://down.guide/census.
How long did it last?
14m, from 2025-07-03 01:58 UTC to 2025-07-03 02:11 UTC, by the times Census posted.
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.