- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on 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 0m it lasted.
Anything that failed between 2026-04-29 17:14 UTC and 2026-04-27 17:00 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 1
- resolved
Summary: From 10:20 AM to 3:00 PM PDT on April 27th, a global Databricks Compute outage resulted in failed audience preview queries across external workspaces. Details: The disruption was caused by an upstream infrastructure failure at Databricks, which prevented some preview queries from executing successfully. This issue was localized to the dashboard preview tool; real-time event delivery and audience activations were not impacted. Resolution: The underlying compute issue has been resolved by the vendor. We have confirmed that preview functionality is fully restored and 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-05e3101467
Is Segment still down?
No, this incident was resolved 2026-04-27 17:00 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
0m, from 2026-04-29 17:14 UTC to 2026-04-27 17:00 UTC, by the times Segment posted.
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.