IP Address Change for Database Requests

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 31m it lasted.

  Anything that failed between 2025-01-30 02:59 UTC and 2025-01-30 03:31 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 4

1. investigatingJan 30, 2025, 2:59 AM UTC

   Due to a networking misconfiguration, requests originating from Census's database access service are originating from IPs that we have not previously advertised. If your database is configured to reject requests that are not from Census' IP addresses, syncs will start failing. We are investigating the root cause of the issue and it is our intent to restore service from the original IP addresses; we do not expect customers to need to reconfigure their databases at this time. More updates will be posted here.

   provider

2. identifiedJan 30, 2025, 3:12 AM UTC

   We have identified the root cause and are applying a fix to the networking configuration.

   provider

3. monitoringJan 30, 2025, 3:24 AM UTC

   We have rolled back the service to a previous configuration and we are monitoring our system to ensure database / warehouse connectivity returns to normal levels.

   provider

4. resolvedJan 30, 2025, 3:31 AM 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.