Skip to main content
Clearbit

Delays in Segment Destination Delivery

Partial outage Lasted 31m · started · Clearbit's page

Level
confirmed
Worst impact
Partial outage
Components
Segment
Down Index
36of 100

What to do

  • Check whether you use Clearbit Segment. 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-08-07 19:24 UTC and 2025-08-07 19:55 UTC may need a replay.
  • Subscribe to Clearbit's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=clearbit works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Clearbit 3

  1. investigating

    We're currently experiencing delays in delivering data to Clearbit destinations integrated via our Segment integration. While there was a temporary failure in processing (resulting in data not being delivered), we expect the affected data to be reprocessed. We're actively working to ensure full delivery and will provide updates as processing progresses.

    provider

  2. identified

    We've implemented a fix, and Segment destination processing is now resuming. Affected data should begin processing shortly, and we're monitoring the system to ensure successful delivery.

    provider

  3. resolved

    The issue affecting Segment destination processing has been resolved. All data has been successfully processed, and the system is operating normally. We're continuing to monitor to ensure stability.

    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-0a2f6623df

Is Clearbit still down?

No, this incident was resolved 2025-08-07 19:55 UTC. For Clearbit's live state, see https://down.guide/clearbit.

How long did it last?

31m, from 2025-08-07 19:24 UTC to 2025-08-07 19:55 UTC, by the times Clearbit posted.

What was affected?

Clearbit named Segment.

What caused it?

Clearbit hasn't published a root cause. If it does, it shows here.

Where does this come from?

Clearbit's official status page, https://status.clearbit.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.