Skip to main content
Segment

Intercom cloud sources failing to fetch data

Degraded Lasted 14h 20m · started · Segment's page

Level
confirmed
Worst impact
Degraded
Components
Cloud Sources (US), Cloud Sources (EU)
Regions
eu, us
Down Index
31of 100

What to do

  • Check whether you use Segment Cloud Sources (US), Cloud Sources (EU) in eu, us. 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 14h 20m it lasted.

    Anything that failed between 2025-10-20 10:11 UTC and 2025-10-21 00:31 UTC may need a replay.
  • Subscribe to Segment's feed to hear about the next one first. RSS feed

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

Updates from Segment 4

  1. identified

    Segment is observing service unavailable error from intercom APIs.

    provider

  2. monitoring

    We are monitoring the recovery of Intercom cloud sources after experiencing data fetching issues. Intercom has reported their services are recovering from the incident. We are closely watching data ingestion to ensure full restoration.

    provider

  3. monitoring

    Intercom EU cloud sources are now fully operational and data ingestion has been restored. All services are functioning normally

    provider

  4. resolved

    Intercom cloud sources data fetching issues have been resolved. All services are now operating normally.

    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-04068edeab

Is Segment still down?

No, this incident was resolved 2025-10-21 00:31 UTC. For Segment's live state, see https://down.guide/segment.

How long did it last?

14h 20m, from 2025-10-20 10:11 UTC to 2025-10-21 00:31 UTC, by the times Segment posted.

What was affected?

Segment named Cloud Sources (US), Cloud Sources (EU) in eu, us.

What caused it?

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

Where does this come from?

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