Rippling: Issue with automatic agent installation after MDM enrollment

Impact: majorStatus: resolvedStarted 2026-01-28 00:30 UTCResolved 2026-01-28 00:30 UTC (0 min)1 updateSource: stspg.io

Summary

Rippling reported a major incident in which its agent did not automatically install after MDM enrollment, with cases observed on the morning of Jan 26. The recorded start and resolution were both 2026-01-28 00:30 UTC (computed duration: 0 min); Rippling said it found the root cause and fixed the issue, without specifying either.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Timeline of updates

resolved2026-01-28 00:30 UTC
On the morning of Jan 26, we saw cases where the Rippling agent did not automatically install after MDM enrollment. We found the root cause and fixed the issue. It is now resolved.

Rewindex changes for this incident

Major incident: Issue with automatic agent installation after MDM enrollment 2026-01-28 00:30 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