Oct <var data-var='date'> 1</var>, <var data-var='time'>17:36</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'> 1</var>, <var data-var='time'>15:14</var> UTC Monitoring - Connectivity to Redis in azure-eastus too has been restored. Syncs are now completing successfully. We are continuing to monitor the situation. Oct <var data-var='date'> 1</var>, <var data-var='time'>14:53</var> UTC Update - Connectivity to Azure Redis continues to be spotty in azure-eastus. Some syncs may see recovery, at least intermittently. Oct <var data-var='date'> 1</var>, <var data-var='time'>14:20</var> UTC Identified - Syncs running in our azure-eastus region are currently not succeeding due to a partial service outage

Sync Outage in azure-eastus region

Sep <var data-var='date'>16</var>, <var data-var='time'>15:33</var> UTC 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. Sep <var data-var='date'>16</var>, <var data-var='time'>11:42</var> UTC 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.

LinkedIn Sync Failures - server responding with status 426

Sep <var data-var='date'> 9</var>, <var data-var='time'>17:33</var> UTC Resolved - A backend change caused Activation workspaces to fail to load. We rolled back the change which allowed the app to load successfully. Only UI components were impacted, sync runs were unaffected. Sep <var data-var='date'> 9</var>, <var data-var='time'>17:10</var> UTC Monitoring - The change has been rolled back and the app is now loading. Sep <var data-var='date'> 9</var>, <var data-var='time'>17:07</var> UTC Update - We are continuing to work on a fix for this issue. Sep <var data-var='date'> 9</var>, <var data-var='time'>16:47</var> UTC Identified - The issue has been identified and the engineering team is working on safely rolling back the change. Sep <var data-var='date'> 9</var>, <var data-var='time'>16:41</var> UTC Investigating - We are currently investigating the issue where the app is failing to load.

App failing to load

Sep <var data-var='date'> 8</var>, <var data-var='time'>22:06</var> UTC Resolved - This incident has been resolved. A recent change prevented some UI jobs from being processed, causing some notifications to be delayed and dataset previews, sync configuration fields, and connection tests to fail to load successfully Sep <var data-var='date'> 8</var>, <var data-var='time'>21:02</var> UTC Monitoring - A fix has been implemented and we are monitoring results. Sep <var data-var='date'> 8</var>, <var data-var='time'>20:04</var> UTC Investigating - Some organizations are currently experiencing increased latency when running connection tests and loading source and destination objects within the sync editor. Investigation is still ongoing.

Degraded UI performance

Aug <var data-var='date'>26</var>, <var data-var='time'>14:11</var> UTC Resolved - The incident has now been resolved. All Facebook (Meta) syncs will recover on their next triggered or scheduled run. Aug <var data-var='date'>26</var>, <var data-var='time'>13:09</var> UTC Identified - Facebook (Meta) syncs are experiencing failures with the error message - API access disrupted. Go to the App Dashboard and complete Data Use Checkup. An issue related to the Activations Meta app has been identified and a fix is being implemented.

Facebook (Meta) Sync Failures - API access disrupted

Jul <var data-var='date'> 7</var>, <var data-var='time'>18:22</var> UTC Resolved - This incident has been resolved and all systems are operational. Jul <var data-var='date'> 7</var>, <var data-var='time'>16:01</var> UTC Monitoring - A fix has been implemented and we're monitoring the results. Jul <var data-var='date'> 7</var>, <var data-var='time'>15:54</var> UTC Update - The web application is operational and sync execution is starting. Jul <var data-var='date'> 7</var>, <var data-var='time'>15:47</var> UTC Identified - An issue related to a recent database migration has been identified. The engineering team is working on safely rolling back the change. Jul <var data-var='date'> 7</var>, <var data-var='time'>15:45</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'> 7</var>, <var data-var='time'>15:45</var> UTC Investigating - The engineering team is currently investigating a production issue.

Service incident impacting app and sync execution

May <var data-var='date'>21</var>, <var data-var='time'>17:00</var> UTC Resolved - 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.

Microsoft Advertising Sync Failures

Feb <var data-var='date'>26</var>, <var data-var='time'>00:32</var> UTC Resolved - The incident has been resolved. Issue determined to be caused due to a configuration change. Configuration change has been reverted. Feb <var data-var='date'>26</var>, <var data-var='time'>00:28</var> UTC Investigating - We are currently investigating the issue.

Census Web Outage

Jan <var data-var='date'>29</var>, <var data-var='time'>20:40</var> UTC Resolved - This incident has been resolved. Jan <var data-var='date'>29</var>, <var data-var='time'>19:30</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jan <var data-var='date'>29</var>, <var data-var='time'>19:15</var> UTC Investigating - We are currently investigating this issue.

Degraded performance of Web & Sync Runs.

Jan <var data-var='date'>29</var>, <var data-var='time'>02:00</var> UTC Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>29</var>, <var data-var='time'>01:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>27</var>, <var data-var='time'>18:25</var> UTC Scheduled - We will be undergoing scheduled maintenance during this time.

Database Maintenance

Jan <var data-var='date'> 5</var>, <var data-var='time'>20:24</var> UTC Resolved - 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. Jan <var data-var='date'> 5</var>, <var data-var='time'>19:05</var> UTC Monitoring - The web is now operating normally, along with Sync Runs. We are monitoring the system for overall health. Jan <var data-var='date'> 5</var>, <var data-var='time'>18:34</var> UTC Update - Syncs are now operational. Users may be experiencing issues loading Sync Configuration and Sync Run details on the web. Jan <var data-var='date'> 5</var>, <var data-var='time'>16:47</var> UTC Update - 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. Jan <var data-var='date'> 5</var>, <var data-var='time'>15:59</var> UTC Update - We are still seeing degraded performance and in some cases failing syncs. We are continuing efforts to mitigate as the system repairs. Jan <var data-var='date'> 5</var>, <var data-var='time'>15:27</var> UTC Update - 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. Jan <var data-var='date'> 5</var>, <var data-var='time'>15:17</var> UTC Identified - Census is currently having issues running Syncs and rendering the Website. Engineers have identified the issue and are remediating.

Census Full Outage

Dec <var data-var='date'>11</var>, <var data-var='time'>19:07</var> UTC Resolved - 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. Dec <var data-var='date'>11</var>, <var data-var='time'>18:39</var> UTC Monitoring - Census Web has recovered and we are analyzing Sync Runs for impact. Dec <var data-var='date'>11</var>, <var data-var='time'>18:32</var> UTC Identified - 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.

Census Web Outage and Sync Delays

Nov <var data-var='date'>12</var>, <var data-var='time'>20:01</var> UTC Resolved - This incident has been resolved. Nov <var data-var='date'>12</var>, <var data-var='time'>18:30</var> UTC Update - 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. Nov <var data-var='date'>12</var>, <var data-var='time'>18:30</var> UTC Monitoring - 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. Nov <var data-var='date'>12</var>, <var data-var='time'>17:41</var> UTC Identified - The issue has been identified and a fix is being implemented.

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

Oct <var data-var='date'>29</var>, <var data-var='time'>03:09</var> UTC Resolved - Delays have been resolved. Syncs are running normally again. Oct <var data-var='date'>29</var>, <var data-var='time'>02:53</var> UTC Identified - 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. Oct <var data-var='date'>29</var>, <var data-var='time'>02:13</var> UTC Investigating - 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.

Minor Delays in Census Syncs (US Region)

Oct <var data-var='date'>21</var>, <var data-var='time'>00:26</var> UTC Resolved - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>20:51</var> UTC Update - Our systems show sustained recovery and remain stable. We will continue to monitor for any further issues. Oct <var data-var='date'>20</var>, <var data-var='time'>18:52</var> UTC Monitoring - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>17:54</var> UTC Update - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>16:07</var> UTC Update - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>13:43</var> UTC Identified - 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.

Delays in Background Jobs

Oct <var data-var='date'>20</var>, <var data-var='time'>07:00</var> UTC Resolved - 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.

Major Service Degradation

Sep <var data-var='date'>19</var>, <var data-var='time'>16:50</var> UTC Resolved - 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. Sep <var data-var='date'>19</var>, <var data-var='time'>16:41</var> UTC Investigating - 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.

Intermittent Page Load Fails

Jul <var data-var='date'>15</var>, <var data-var='time'>18:44</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>15</var>, <var data-var='time'>18:31</var> UTC Monitoring - We have updated the our configurations for sending emails and we are currently verifying the fix. Jul <var data-var='date'>15</var>, <var data-var='time'>16:35</var> UTC Investigating - 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

Census unable to send any emails

Jul <var data-var='date'> 3</var>, <var data-var='time'>02:11</var> UTC Resolved - AWS has marked this as resolved. Jul <var data-var='date'> 3</var>, <var data-var='time'>01:58</var> UTC 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

AWS Incident Being Monitored - No Production Impact Yet

Jun <var data-var='date'>12</var>, <var data-var='time'>21:05</var> UTC Resolved - Census systems remain unaffected as GCP comes back online. We are now seeing the majority of our GCP hosted customers have successful syncs. Jun <var data-var='date'>12</var>, <var data-var='time'>20:19</var> UTC Update - Our monitoring systems continue to see a sustained error rate when communicating with Google BigQuery. We will monitor and report when the issue is resolved from Census' perspective. Google Cloud has provided additional information on their status page, located here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW Jun <var data-var='date'>12</var>, <var data-var='time'>18:37</var> UTC Update - Internal monitoring indicates that syncs to and from BigQuery started experiencing increased failure rates at around 18:05 UTC. The rate of failures is now decreasing but has not returned to usual levels. Jun <var data-var='date'>12</var>, <var data-var='time'>18:30</var> UTC Monitoring - We are aware of the current GCP outage and we are monitoring its impact on Census syncs to and from Google and Google Cloud Resources. Census does not run any critical components on GCP but we do use GCP resources, including Cloud Storage, to facilitate interaction with BigQuery and other Google Cloud resources.

GCP Outage May Affect Syncs to and from Google Resources

Jun <var data-var='date'> 6</var>, <var data-var='time'>18:18</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 6</var>, <var data-var='time'>17:52</var> UTC Monitoring - Some syncs started failing with the following error at 12:18pm (EST) "ActiveRecord::StatementInvalid: PG::UndefinedColumn: ERROR: column sync_configurations.new_diff_timestamp_expression_id does not exist" This was due to a brief issue during a schema update. The problem has been resolved, and we are monitoring.

Sync Runs Failing with Undefined Column Error

Jun <var data-var='date'> 4</var>, <var data-var='time'>20:54</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 4</var>, <var data-var='time'>20:43</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'> 4</var>, <var data-var='time'>20:24</var> UTC Update - A fix for this issue is currently being deployed and will be in place in the next 15-30 minutes Jun <var data-var='date'> 4</var>, <var data-var='time'>20:11</var> UTC Identified - The Census sync list UI is not loading for some customers. We have identified a faulty deployment and we are reverting it. The sync engine is not affected.

Sync list UI not loading

May <var data-var='date'>28</var>, <var data-var='time'>14:00</var> UTC Resolved - During a window of time from 9:58 am EST until 10:32 am EST, the Census web UI, and a portion of the Census Public Management API experienced an outage. Sync Runs were unaffected and operated normally.

Web Outage

Apr <var data-var='date'>21</var>, <var data-var='time'>19:33</var> UTC Resolved - A recent code change introduced a bug resulting in some syncs failing with the message "T.cast: Expected type T::Struct, got type TrueClass". This impacted sync runs where there were no incremental changes identified and the source connection utilizes the Advanced Sync Engine. We identified the problematic change, and have reverted. Syncs are now running successfully.

Some syncs failing with "T.cast: Expected type T::Struct, got type TrueClass"

Apr <var data-var='date'>16</var>, <var data-var='time'>23:54</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>16</var>, <var data-var='time'>23:36</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>16</var>, <var data-var='time'>23:31</var> UTC Identified - We've identified an issue that caused background jobs to be delayed. The issue does not impact running syncs.

Is Census down?

Census status is UP

Lastest published events

Sync Outage in azure-eastus region

LinkedIn Sync Failures - server responding with status 426

App failing to load

Census Services, Components and Regions

Recent Census events

Sync Outage in azure-eastus region

LinkedIn Sync Failures - server responding with status 426

App failing to load

Degraded UI performance

Facebook (Meta) Sync Failures - API access disrupted

Service incident impacting app and sync execution