Companies / Rippling / incidents
Rippling: Notification delay
Rippling reported a major notification degradation causing 2–15 minute authentication delays, starting 2025-10-27 15:23 UTC and resolved at 2025-10-27 18:38 UTC (3 h 14 min). Scheduled notifications were temporarily suspended to reduce database load; delivery recovered within the 10-second SLA, scheduled jobs resumed, and delayed scheduled notifications were being sent.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: NotificationsPlatform Tools - NotificationsRippling App
Timeline of updates
- investigating
Customers may be experiencing a delay in notifications causing authentication delays. We are observing a 2 - 15 minute delay in notifications. This is under investigation.
- investigating
We are temporarily suspending scheduled notification jobs in order to bring down the database load so that all other notifications -- including time-sensitive authentication notifications -- can recover to be delivered within SLA.
- investigating
We have partial recovery where new notifications are being sent within the SLA of 10 seconds. Scheduled notifications continue to be suspended.
- monitoring
The notification service has been restored, and notifications are now properly getting sent within the SLA. Scheduled notification jobs have been restored, so moving forward they will be sent at the scheduled time. Scheduled notifications that were scheduled to be sent during the suspended period -- between 9:15a PDT to 11:23a PDT -- are being sent now.
- resolved
This incident has been resolved.
Rewindex changes for this incident
- Major incident: Notification delay 2025-10-27 15:23 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Rippling profile · Recent Rippling incidents · Markdown · JSON