Segment's Destinations component broke for 8 hours 36 minutes on 1 October, with the Braze Web Event Delivery destination failing to deliver events. This was a fault on Segment's side of the pipeline, not yours.
Started
03:30 UTC
Duration
Lasted 8h 36m
Source
IsDown
Next time
Segment is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Destinations
What happened?
The incident started at 03:30 UTC and ran until resolution at 12:03 UTC, a total of 8h 36m. Segment's status page lists it under a single component, Destinations, and names the specific path affected as Braze Web Event Delivery. The first update says the issue was reported by one customer and that Segment was investigating, which tells you this was caught from a single account rather than broad monitoring. At 04:34 Segment says the issue was identified and a fix was being implemented. At 06:00 Segment moved to monitoring, saying a fix had been implemented and results were being watched. Nothing further was filed until the resolved update at 12:03, six hours later, so you have no visibility into what Segment was actually checking in that gap. No user reports were filed during the window on this page, so this was not something customers were widely flagging in this record. Segment's own wording never goes beyond "experience event delivery issue", no further detail on what inside the delivery path broke or why. Over the last 90 days Segment has logged 11 incidents with a median duration of 4 hours 49 minutes, so this one ran longer than typical for this provider. Across all time Segment averages 4.5 incidents a month, putting this in line with a provider whose destinations pipeline fails somewhat routinely.
Learning
This incident sat entirely inside Segment's delivery pipeline to a downstream destination, a layer you cannot see by watching your own endpoints. Your product's health checks would have stayed green the whole time because nothing on your side was broken, the events simply weren't reaching Braze once they left Segment's hands. That is why a single customer report was what triggered Segment's own investigation rather than any internal alarm on their end. Over Segment's last 30 days, UptimeRobot's own monitoring recorded 5 incidents with a median duration of 4h 49m, all resolved, which gives you an independent read on how often this kind of destination failure recurs. The general shape to recognise is simple: data leaves your system fine, Segment accepts it, and somewhere in the forwarding step to a third party it stalls without anything in your own stack showing a fault. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
