We are observing elevated ETIMEDOUT errors from Yahoo DSP destination.
Jan 22, 13:33 UTCJan 22, 17:37 UTC
Duration
4h 4m
Impact
Major
Root cause
Not disclosed
Segment, 90 days
11 incidents
Affected
Streaming Destinations (US)Streaming Destinations (EU)Streaming Destinations - Streaming Destinations (US)Streaming Destinations - Streaming Destinations (EU)
Final update
This incident has been resolved.
Timeline
- Resolved · Jan 22, 17:37 UTC
This incident has been resolved.
- Monitoring · Jan 22, 16:02 UTC
The incident has been mitigated and we are monitoring the destination. We will provide updates as more information becomes available from Yahoo team.
- Identified · Jan 22, 14:36 UTC
We are experiencing "504 - Gateway Time-out" errors when communicating with the Yahoo DSP endpoint. We are working with Yahoo support team to get this resolved. We will provide updates as more information becomes available.
- Investigating · Jan 22, 13:33 UTC
We are observing elevated ETIMEDOUT errors from Yahoo DSP destination. We are currently investigating the issue.
More from Segment
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1619:40 UTC | Actions S3 is currently experience formatting issues with the delivered events | minor | 2h 10m |
| Sep 1014:28 UTC | SSO Login Issues with the Segment App | major | 1h 11m |
| Sep 318:30 UTC | Issue with Engage UI | major | 4h 11m |
| Sep 301:04 UTC | Segment App UI Issue with Profile Traits with no recent activity | minor | 21h 38m |
| Aug 1817:49 UTC | Intermittent Segment application login errors | major | 4h 13m |
| Aug 615:19 UTC | Google ads destination intermittent delivery failure | minor | 14h 44m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.