Rippling outage, January 2026: Issue with automatic agent installation after MDM enrollment
Rippling reported and resolved an incident: Issue with automatic agent installation after MDM enrollment. It lasted 29 hours.
OKResolved
From Rippling's official status page, in their words.
What happened
- Started
- Resolved
- Duration
- 29 hours
- Impact
- major
- Investigating
- Identifiednot posted
- Monitoringnot posted
- Resolved
Why it happened
Rippling has not given a cause in its updates. We never guess one.
How it was resolved
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.
Timeline
Oldest first, from the first notice to the resolution. From Rippling's official status page, in their words.
- resolved
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.
What this means for a business (and what to check now)
- Retry anything that failed during the 29 hours.
- Enter any payments, bookings or jobs you took another way.
- If a deadline fell inside the window, keep this page as your record of the outage.
The full guide: what to do when a service you rely on is down
Other Rippling incidents
- Issues editing Supergroups, resolved after 1.4 hours
- QuickBooks data import delayed for some customers, resolved after 10.9 hours
- Rippling AI is down, resolved after 11 minutes
- Products partially degraded, resolved after 1.8 hours
- Issues using 1Password passkeys, resolved after 25.9 hours
Hear about the next Rippling incident as it starts
Free email alerts when the official status changes, with what to do while it is down.