Live / Rippling / Incident
Rippling: Products partially degraded
Rippling · rippling.comMajor incidentResolved2026-10-15 20:55 UTC
Public — what happened
Summary
Rippling said on October 15, 2026 at 19:07 UTC that its products were seeing more errors than normal, and it rated the problem as major. The company said it had pinpointed the part of its system involved and was working to contain the issue, though it did not name a specific cause. By 20:08 UTC Rippling reported that the problem had been mitigated and service had fully recovered, and it marked the incident resolved at 20:55.
Affected
Rippling App
Timeline
- Started — 2026-10-15 19:07 UTC
- Investigating — 2026-10-15 19:07 UTC
- Monitoring — 2026-10-15 20:08 UTC
- Resolved — 2026-10-15 20:55 UTC · 1h 48m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Rippling against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Rippling: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Rippling report →
More from Rippling
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.