Raisely experienced a major incident on October 15, 2025 affecting Marketing Automation and API and 1 more component, lasting 5d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 15, 2025, 10:18 PM UTC
We are currently investigating an issue where default messages are not being created when a new campaign is created or an existing campaign is duplicated.
- investigating Oct 15, 2025, 10:20 PM UTC
We are continuing to investigate this issue.
- identified Oct 16, 2025, 12:46 AM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 16, 2025, 01:11 AM UTC
The engineering team are actively working to restore regular services. As a result of this issue, please note that webhook events for some campaigns are delayed and will resume processing once the issue has been resolved.
- monitoring Oct 16, 2025, 03:41 AM UTC
We have implemented a solution, and the system is currently processing a backlog of interactions. We are closely monitoring progress and appreciate your patience as the system catches up.
- monitoring Oct 16, 2025, 11:43 PM UTC
We are continuing to monitor the system as performance returns to normal.
- monitoring Oct 16, 2025, 11:44 PM UTC
We are continuing to monitor the system as performance returns to normal.
- monitoring Oct 17, 2025, 09:15 PM UTC
We are continuing to monitor the system as performance returns to normal. The queue is steadily decreasing, though some minor processing delays may still occur as it fully clears.
- monitoring Oct 20, 2025, 04:23 AM UTC
We are continuing to experience delays in backend processing due to a backlog of interactions. Our team is actively monitoring the backlog and investigating improvements to increase processing speed. We apologize for the inconvenience and appreciate your patience as we work to resolve this.
- resolved Oct 21, 2025, 12:34 AM UTC
This incident has been resolved. We identified the cause and made adjustments to restore normal performance. We appreciate your patience and understanding while we worked to resolve this.