Rewindex

ChangesCourierMessage Send Delays for Legacy Segment to Send Message Integration

Courier: Major incident: Message Send Delays for Legacy Segment to Send Message Integration

Major incidentmajor (vendor)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Courier removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Message Send Delays for Legacy Segment to Send Message Integration
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2022-07-25 20:45 UTC
AddedResolved time#5
Before: not present
After: 2022-07-26 05:16 UTC
AddedAffected components#6
Before: not present
After: Integrations: Inbound to Courier - Segment Destinations
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating an issue where Send messages triggered by the Segment Event track/ integration are not being sent. Customers using the Segment Event track/ integration with Automations appear not to be impacted.
AddedUpdateidentified#8
Before: not present
After: We have identified the issue and are preparing a release that will resolve it for new incoming Segment events. We are working to identify historical segment events that should have triggered sends that were impacted.
AddedUpdateidentified#9
Before: not present
After: We are continuing to work on a fix for this issue.
AddedUpdatemonitoring#10
Before: not present
After: We have released a fix for new incoming Segment events. We are monitoring to confirm send volume for Segment to Send returns to normal.
AddedUpdatemonitoring#11
Before: not present
After: We have confirmed our deployed fix has resolved the issue for new incoming events. We are continue to work on resolution for historical segment events that did not trigger message sends.
AddedUpdateresolved#12
Before: not present
After: We have finished measuring the impact and will be reaching out to affected customers.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Monday, July 25, 2022

1 incident change

All Courier changesCourier profileMarkdownJSON