August 27th, 2026 - Service Disruption
Service Disruption on August 27, 2026
Status: Resolved
Summary
On August 27, CultureBot experienced a backend service disruption that affected message delivery across Slack, Teams, and the web app for part of the morning. Service has been fully restored.
What was affected
During the disruption, some scheduled messages did not send on time, including celebration messages, manager alerts, employee intros, and shoutout day reminders.
Shoutouts sent during the disruption were largely recoverable and delivered once service was restored. A small number may not have gone through.
For some accounts, a few messages posted more than once as the system caught up after the disruption. This duplication was isolated to this incident. Apologies for any confusion this caused.
Current status
- Celebration messages missed during the disruption were sent at 2pm CT today.
- Other missed nudges (manager alerts, employee intros, shoutout day reminders) were reviewed and sent at 2pm CT today for any affected accounts.
- Shoutouts that were not recoverable will need to be re-sent manually.
If you have a paid account with CultureBot and were affected by any of the above, your CSM will be in touch directly to give you an update by end of day, August 27th, 2026.
Duplicate shoutouts or points
If the recovery process resulted in a duplicate shoutout or duplicate points, please reach out to your CSM directly or support@getculturebot.com and they'll get it corrected.
How We Handle
We have an automated quality control audit that runs every night. So there’s never a risk of celebrations being missed without us knowing. We also have automations to catch when this happens, often pushing a "catch up" message in the same hour or day. But as a backstop, we’ll always know within a day if something was missed and reach out to you for clarity.
Questions
Contact your CultureBot Customer Success Manager or support@getculturebot.com for assistance.