Courier: Internal Courier Error Issue
Affected components: API
Timeline of updates
- identified
The Courier team has identified an issue where messages fail due to an "Internal Courier Error" in the test environment. Our team found the root cause and are working to mitigate the issue.
- identified
We have tested the fix for "Internal Courier Error" and will be releasing it to production soon.
- identified
A fix has been merged and will fully deploy within the next hour. Updates to follow.
- monitoring
The fix has landed in production and we will be monitoring for any more "Internal Courier Errors". We will be working on reprocessing any dropped messages caused by this issue.
- monitoring
Messages with tags are no longer impacted, and error has been resolved. The team is working on reprocessing dropped messages.
- monitoring
The team is still working on reprocessing dropped messages caused by this issue. Send pipeline is operational.
- resolved
All impacted messages have been reprocessed.
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.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).