Changes / Rippling / Access denied

Rippling: Critical incident: Access denied

Summary

Rippling reported a critical incident in which some users saw "Access denied" when accessing Rippling. It started and was resolved at 2026-07-16 09:00 UTC, with a computed duration of 0 min; Rippling said the issue was fully mitigated and service was fully operational again.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

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

What changed

AddedTitle#1
Before: not present
After: Access denied
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-07-16 09:00 UTC
AddedResolved time#5
Before: not present
After: 2026-07-16 09:00 UTC
AddedUpdateresolved#6
Before: not present
After: Rippling displayed "Access denied" to some users accessing Rippling. The issue has been fully mitigated and Rippling is fully operational again.

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

History of this incident

When (UTC)ChangeKind
Critical incident: Access denied (this change)
Rippling reported a critical incident in which some users saw "Access denied" when accessing Rippling. It started and was resolved at 2026-07-16 09:00 UTC, with a computed duration of 0 min; Rippling said the issue was fully mitigated and service was fully operational again.
Major incident

All Rippling changes → · Rippling profile · Markdown · JSON