If events stopped showing up in your destinations on 26 October, the fault was on Segment's side. Event delivery failed for 12h 46m, caused by a problem Segment has not explained beyond saying it affected "a small number" of customers.
Started
13:35 UTC
Duration
Lasted 12h 46m
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?
Segment's status page logged one incident on 26 October, affecting the Destinations component. It started at 13:35 UTC with a short note: a small number of events were failing to deliver, and Segment was investigating. A follow-up three minutes later said only that investigation was continuing. After that, nothing was posted for over twelve hours. The next and final update came at 02:19 UTC, when Segment marked the incident resolved, saying it had identified and mitigated the cause and that affected customers should contact support to request a replay of missed events. No root cause was given at any point. Segment never named what broke, only that it had a fix. The total time between the first report and resolution was 12h 46m. No user reports were logged in this window, which fits Segment's own description of a small number of affected customers rather than a broad outage. This is Segment's only incident of the day, and the single filing is the entire record of what happened. Over the past 90 days Segment has logged 10 incidents with a median duration of 6 hours 43 minutes, so this one ran nearly double the usual length.
Learning
Event delivery failures like this one happen inside Segment's pipeline, after your application has already sent the data and received a success response. That is why checking your own endpoints or your app's health would not have shown you anything wrong. Over the last 30 days, UptimeRobot's own checks against Segment recorded 3 incidents with a median duration of 8h 36m, all now resolved, numbers that sit close to what Segment itself reports for this kind of event. The gap between "my app looks fine" and "my events are actually landing in destinations" is exactly where this incident lived, and it is invisible from your side until customers start asking why a destination has stale data. Replays after the fact can recover some of what was lost, but only if you know to ask, and Segment's own notice is the only trigger for that. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.