Rippling: vendor-reported critical incident on September 29 (tracked 7h 28m)
Sep 29, 08:30 PM → Sep 30, 03:59 AM · 7h 28m · high
Rippling reported a critical-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 7h 28m, from Tue, 29 Sep 2026 20:30:14 GMT to Wed, 30 Sep 2026 03:59:01 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.
Impact
PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.
Incident timeline
- Sep 29, 08:30 PM
The vendor reported a critical-impact incident on its own status page; PulseWatch began tracking it
- Sep 29, 08:30 PM
Status updated: possible issue
- Sep 30, 03:59 AM
PulseWatch closed the incident
Official updates
- Sep 29, 08:30 PM
Rippling reported the incident on its status page.
View official source