# Rippling: Issue with automatic agent installation after MDM enrollment

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-01-28 00:30 UTC · Resolved: 2026-01-28 00:30 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://stspg.io/gsphl6yn50w3](https://stspg.io/gsphl6yn50w3)
- [Company: Rippling](https://rewindex.com/company/rippling.md)

## 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, sol)_
## Timeline of updates

- **resolved** 2026-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

- 2026-01-28 00:30 UTC: [Major incident: Issue with automatic agent installation after MDM enrollment](https://rewindex.com/change/i1aa2d45b031b20.md)


---
Canonical: https://rewindex.com/company/rippling/incidents/74stlvlf7bx2 · Markdown: https://rewindex.com/company/rippling/incidents/74stlvlf7bx2.md · JSON: https://rewindex.com/api/v1/companies/rippling/incidents/74stlvlf7bx2 · Generated 2026-10-18T11:33:33.636Z