Census Outage History

Census is up right now

Census had 12 outages in the last 2 years totaling 26h 4m of downtime — averaging 0.5 incidents per month.

There were 12 Census outages since July 15, 2025 totaling 26h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getcensus.com

Critical July 7, 2026

Service incident impacting app and sync execution

Detected by Pingoru
Jul 07, 2026, 03:45 PM UTC
Resolved
Jul 07, 2026, 06:22 PM UTC
Duration
2h 36m
Affected: Census Sync Management UISync Engine
Timeline · 6 updates
  1. investigating Jul 07, 2026, 03:45 PM UTC

    The engineering team is currently investigating a production issue.

  2. investigating Jul 07, 2026, 03:45 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 07, 2026, 03:47 PM UTC

    An issue related to a recent database migration has been identified. The engineering team is working on safely rolling back the change.

  4. identified Jul 07, 2026, 03:54 PM UTC

    The web application is operational and sync execution is starting.

  5. monitoring Jul 07, 2026, 04:01 PM UTC

    A fix has been implemented and we're monitoring the results.

  6. resolved Jul 07, 2026, 06:22 PM UTC

    This incident has been resolved and all systems are operational.

Read the full incident report →

Minor May 21, 2026

Microsoft Advertising Sync Failures

Detected by Pingoru
May 21, 2026, 05:00 PM UTC
Resolved
May 21, 2026, 05:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 22, 2026, 12:24 AM UTC

    Syncs to Microsoft Advertising temporarily experienced failures with an error message like "OAuth2::Error: invalid_client" from approximately 05/21/2026 17:00 UTC - 05/21/20206 23:19 UTC. This error was the result of the Activations Microsoft Advertising app configuration and it has now been resolved. Any impacted syncs will recover on their next scheduled run.

Read the full incident report →

Critical February 26, 2026

Census Web Outage

Detected by Pingoru
Feb 26, 2026, 12:28 AM UTC
Resolved
Feb 26, 2026, 12:32 AM UTC
Duration
4m
Affected: Census Sync Management UI
Timeline · 2 updates
  1. investigating Feb 26, 2026, 12:28 AM UTC

    We are currently investigating the issue.

  2. resolved Feb 26, 2026, 12:32 AM UTC

    The incident has been resolved. Issue determined to be caused due to a configuration change. Configuration change has been reverted.

Read the full incident report →

Minor January 29, 2026

Degraded performance of Web & Sync Runs.

Detected by Pingoru
Jan 29, 2026, 07:15 PM UTC
Resolved
Jan 29, 2026, 08:40 PM UTC
Duration
1h 25m
Affected: Census Sync Management UI
Timeline · 3 updates
  1. investigating Jan 29, 2026, 07:15 PM UTC

    We are currently investigating this issue.

  2. monitoring Jan 29, 2026, 07:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 29, 2026, 08:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 5, 2026

Census Full Outage

Detected by Pingoru
Jan 05, 2026, 03:17 PM UTC
Resolved
Jan 05, 2026, 08:24 PM UTC
Duration
5h 7m
Affected: Census Sync Management UISync Engine
Timeline · 7 updates
  1. identified Jan 05, 2026, 03:17 PM UTC

    Census is currently having issues running Syncs and rendering the Website. Engineers have identified the issue and are remediating.

  2. identified Jan 05, 2026, 03:27 PM UTC

    We have identified and triaged the affected system and systems are coming back up now. Web is operational. We will see Sync delays as we scale back up.

  3. identified Jan 05, 2026, 03:59 PM UTC

    We are still seeing degraded performance and in some cases failing syncs. We are continuing efforts to mitigate as the system repairs.

  4. identified Jan 05, 2026, 04:47 PM UTC

    Syncs are currently not operational. Scheduled syncs should still be queuing up but they won't start running at this time. We will provide an update once workers come back up.

  5. identified Jan 05, 2026, 06:34 PM UTC

    Syncs are now operational. Users may be experiencing issues loading Sync Configuration and Sync Run details on the web.

  6. monitoring Jan 05, 2026, 07:05 PM UTC

    The web is now operating normally, along with Sync Runs. We are monitoring the system for overall health.

  7. resolved Jan 05, 2026, 08:24 PM UTC

    This incident has been resolved. Syncs have been running normally as of approximately 1:00pm EST, and the web has been running at normal latencies as of 2:00pm EST. The issue was caused by an indexing change on our side that impacted our ability to run syncs reliably. Recovery was delayed because we needed to rebuild the previous indexes. To avoid any risk of data loss, we chose a safer recovery approach that allowed the system to remain temporarily degraded while repairs were being completed. To restore syncs as quickly as possible, we prioritized sync execution and applied targeted fixes to improve performance. During this time, access to the UI was temporarily down.

Read the full incident report →

Minor December 11, 2025

Census Web Outage and Sync Delays

Detected by Pingoru
Dec 11, 2025, 06:32 PM UTC
Resolved
Dec 11, 2025, 07:07 PM UTC
Duration
35m
Affected: Census Sync Management UISync Engine
Timeline · 3 updates
  1. identified Dec 11, 2025, 06:32 PM UTC

    Census is experiencing an outage on web, and we are experiencing degraded sync run activity. We have identified the cause and have applied the fix. We are monitoring system recovery.

  2. monitoring Dec 11, 2025, 06:39 PM UTC

    Census Web has recovered and we are analyzing Sync Runs for impact.

  3. resolved Dec 11, 2025, 07:07 PM UTC

    After investigation, a very small number of Sync Runs may have failed with an inability to connect to our Redis instance. The majority of syncs that ran between 1:19 pm and 1:28 pm EST will have experienced a few minutes of delay, and recovered automatically.

Read the full incident report →

Minor November 12, 2025

Subset of syncs are failing with, "Passed `nil` into T.must"

Detected by Pingoru
Nov 12, 2025, 05:41 PM UTC
Resolved
Nov 12, 2025, 08:01 PM UTC
Duration
2h 19m
Affected: Sync Engine
Timeline · 4 updates
  1. identified Nov 12, 2025, 05:41 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Nov 12, 2025, 06:30 PM UTC

    The error impacting some customer syncs has now been resolved and syncs are recovering. The syncs impacted were runs with no new data changes to process. This happened due to a recent update that removed the part of our system that correctly handled "no change" scenarios. As a result, syncs without updates failed instead of completing successfully. Syncs with actual data changes were unaffected. We've rolled back the change, and all syncs are now running normally.

  3. monitoring Nov 12, 2025, 06:30 PM UTC

    The error impacting some customer syncs has now been resolved and syncs are recovering. The syncs impacted were runs with no new data changes to process. This happened due to a recent update that removed the part of our system that correctly handled "no change" scenarios. As a result, syncs without updates failed instead of completing successfully. Syncs with actual data changes were unaffected. We've rolled back the change, and all syncs are now running normally.

  4. resolved Nov 12, 2025, 08:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2025

Minor Delays in Census Syncs (US Region)

Detected by Pingoru
Oct 29, 2025, 02:13 AM UTC
Resolved
Oct 29, 2025, 03:09 AM UTC
Duration
56m
Affected: Sync Engine
Timeline · 3 updates
  1. investigating Oct 29, 2025, 02:13 AM UTC

    We are currently investigating minor delays affecting some Census Sync job types in the US region. Most syncs are completing successfully, though some may take longer than usual.

  2. identified Oct 29, 2025, 02:53 AM UTC

    We’ve identified the cause of the minor delays and implemented a fix. Sync performance returning back to normal. We’re monitoring to ensure continued stability.

  3. resolved Oct 29, 2025, 03:09 AM UTC

    Delays have been resolved. Syncs are running normally again.

Read the full incident report →

Minor October 20, 2025

Delays in Background Jobs

Detected by Pingoru
Oct 20, 2025, 01:43 PM UTC
Resolved
Oct 21, 2025, 12:26 AM UTC
Duration
10h 42m
Affected: Sync Engine
Timeline · 6 updates
  1. identified Oct 20, 2025, 01:43 PM UTC

    In our US region, we are seeing increased latency in non-sync background tasks like metadata refreshes and connection tests due to issues scaling up worker load to match demand, as a result of the continued downstream provider outage. We have identified the issue and are now mitigating the impact.

  2. identified Oct 20, 2025, 04:07 PM UTC

    Non-sync background tasks are running normally. Email notifications are still delayed. We have detected syncs that are currently stuck in working state due to issues earlier in the day. We are working to unblock them.

  3. identified Oct 20, 2025, 05:54 PM UTC

    We are seeing increases in Sync runtimes as we continue to experience issues adding new workers to our pool. We are continuing work to mitigate this issue.

  4. monitoring Oct 20, 2025, 06:52 PM UTC

    We're now able to appropriately scale workers to meet demands. We are through our main backlogs (including mail sends), and Sync run latencies have improved substantially. We are still continuing to see transient errors throughout Sync runs, mainly dealing with issues hitting our Redis instances, but the frequency of these errors is continuing to decrease.

  5. monitoring Oct 20, 2025, 08:51 PM UTC

    Our systems show sustained recovery and remain stable. We will continue to monitor for any further issues.

  6. resolved Oct 21, 2025, 12:26 AM UTC

    Our system has been operating normally for the last few hours, and the aforementioned downstream provider has marked their incident as resolved. We are marking the sync engine as operational. Please contact support if you believe you are continuing to see issues.

Read the full incident report →

Notice October 20, 2025

Major Service Degradation

Detected by Pingoru
Oct 20, 2025, 11:09 AM UTC
Resolved
Oct 20, 2025, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 20, 2025, 11:09 AM UTC

    Census experienced major service degradation for running Syncs and on the web for users viewing Sync details for a period of about 3 hours, from 2:46 am EST until 5:30 am EST, due to a large-scale downstream provider outage. All systems are now operational.

Read the full incident report →

Minor September 19, 2025

Intermittent Page Load Fails

Detected by Pingoru
Sep 19, 2025, 04:41 PM UTC
Resolved
Sep 19, 2025, 04:50 PM UTC
Duration
8m
Affected: Census Sync Management UI
Timeline · 2 updates
  1. investigating Sep 19, 2025, 04:41 PM UTC

    We have detected intermittent page load failures on the Census UI due to DNS. Our team is investigating the root cause. Sync runs are unaffected.

  2. resolved Sep 19, 2025, 04:50 PM UTC

    This incident has been resolved and page loads are now fully operational. During a system upgrade it was determined that our DNS resolver returned empty values for app.getcensus.com for a brief point - our team will continue investigating the root cause of why this occurred.

Read the full incident report →

Minor July 15, 2025

Census unable to send any emails

Detected by Pingoru
Jul 15, 2025, 04:35 PM UTC
Resolved
Jul 15, 2025, 06:44 PM UTC
Duration
2h 8m
Affected: Census Sync Management UI
Timeline · 3 updates
  1. investigating Jul 15, 2025, 04:35 PM UTC

    We have identified an incident that has caused Census to stop sending all emails. This includes emails related to sync alerts as well as password reset emails and verification emails for new account signups. We are working to remediate the issue. The Census UI and Sync Engine are not otherwise affected

  2. monitoring Jul 15, 2025, 06:31 PM UTC

    We have updated the our configurations for sending emails and we are currently verifying the fix.

  3. resolved Jul 15, 2025, 06:44 PM UTC

    This incident has been resolved.

Read the full incident report →