Changes / Rippling / Issue with automatic agent installation after MDM enrollment

Rippling: Major incident: Issue with automatic agent installation after MDM enrollment

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 diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 84%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: Issue with automatic agent installation after MDM enrollment
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-01-28 00:30 UTC
AddedResolved time#5
Before: not present
After: 2026-01-28 00:30 UTC
AddedUpdateresolved#6
Before: not present
After: 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.

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Major incident: Issue with automatic agent installation after MDM enrollment (this change)
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.
Major incident

All Rippling changes → · Rippling profile · Markdown · JSON