Live  /  Rippling  /  Incident

Rippling: Performance degraded

Rippling · rippling.comMinor incidentResolved2026-11-11 23:57 UTC
Public — what happened

Summary

Rippling reported a minor incident beginning at 18:12 UTC on 2026-11-11, in which slower performance affected logging in and moving around the site. About twenty minutes later, at 18:32 UTC, the company said it had found the root cause and put a mitigation in place, and that performance had returned to normal while it kept watching. Rippling marked the incident resolved at 23:57 UTC the same day.

Affected

Rippling App, Single Sign-on (SSO)

As listed on Rippling’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 47, 2026, our weekly internet health report.

The full archive is on the Rippling status & history page.

Related: Rippling status & history. SquidGrid is not affiliated with Rippling.