Sync Outage in azure-eastus region

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 3h 16m it lasted.

  Anything that failed between 2026-10-01 14:20 UTC and 2026-10-01 17:36 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.

Root cause

Syncs running in our azure-eastus region are currently not succeeding due to a partial service outage

Updates from Census 4

1. identifiedOct 1, 2026, 2:20 PM UTC

   Syncs running in our azure-eastus region are currently not succeeding due to a partial service outage

   provider

2. identifiedOct 1, 2026, 2:53 PM UTC

   Connectivity to Azure Redis continues to be spotty in azure-eastus. Some syncs may see recovery, at least intermittently.

   provider

3. monitoringOct 1, 2026, 3:14 PM UTC

   Connectivity to Redis in azure-eastus too has been restored. Syncs are now completing successfully. We are continuing to monitor the situation.

   provider

4. resolvedOct 1, 2026, 5:36 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.