Skip to main content
Rippling logo

Is Rippling Down?

No — Rippling is up

Reachable from all 8 checked regions

Average response time: 241ms

Last checked · checks run every 6 hours

Official status page: https://status.rippling.com

Rippling uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
278ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 13 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn
189ms
DNS 73ms TCP 0ms TLS 10ms TTFB 158ms
bom
315ms
DNS 6ms TCP 17ms TLS 58ms TTFB 235ms
cdg
236ms
DNS 34ms TCP 14ms TLS 5ms TTFB 137ms
dfw
312ms
DNS 48ms TCP 15ms TLS 40ms TTFB 179ms
ewr
221ms
DNS 4ms TCP 0ms TLS 17ms TTFB 129ms
fra
136ms
DNS 17ms TCP 0ms TLS 7ms TTFB 105ms
gru
352ms
DNS 124ms TCP 1ms TLS 7ms TTFB 207ms
iad
171ms
DNS 34ms TCP 10ms TLS 4ms TTFB 96ms

What Rippling does

Rippling combines HR, payroll and benefits with IT functions such as single sign-on, device management and app provisioning. Because it is both the HR system and the identity provider at many companies, an outage can block payroll and simultaneously stop staff signing in to the other tools they need that day.

What an outage looks like

Single sign-on fails, so people cannot reach applications that authenticate through Rippling even though those applications are healthy. The Rippling app will not load or hangs after login. Payroll runs fail to submit or stall in review. Time and scheduling entries do not save, and device management actions queue without applying to laptops.

What to do about it

Check status.rippling.com, which lists Single Sign-on, Authentication, Payroll, Benefits, Time, Device and Inventory Management and the Platform API as separate components, so a payroll problem does not always mean sign-in is affected. Tell people not to sign out of applications they are already in. If a payroll deadline is close, contact support rather than retrying the run.

Is it down for everyone, or just you?

If this page says Rippling is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

BambooHR
BambooHR
Okta
Okta
Google Workspace
Google Workspace
1Password
1Password

Rippling outage FAQ

Why can I not sign in to other apps when Rippling is down?
Rippling acts as an identity provider, so applications behind its single sign-on refuse new sessions during an authentication incident even though those applications are running normally. People already signed in usually keep working until their session expires. This is why signing out mid-incident is worth avoiding: it cannot be undone.
Will payroll still run if Rippling has an outage?
Payroll is reported as its own component and can be affected independently of the rest of the platform. Short incidents rarely move a pay date, but a failure close to a submission deadline is worth escalating to support rather than retrying quietly, since payroll cutoffs are set by banks and tax authorities and do not shift for an outage.
Is Rippling down or is my company's configuration broken?
If colleagues on the same account are unaffected, the cause is more likely a role, permission or app assignment than an incident. Rippling separates Authentication from the app itself, so match your symptom to a component first. A configuration change made recently by an administrator explains far more single-user failures than platform incidents do.
Do time and attendance entries survive an outage?
Entries the system accepted are stored. Entries submitted while the platform was failing may not have saved, and staff often assume they did. After an incident, asking people to check their timesheets is worth the small effort, because a missing entry discovered at approval time is much harder to reconstruct than one checked the same day.
Does an outage affect devices already enrolled in Rippling?
Laptops keep working normally. Device and Inventory Management handles policies and actions sent to machines, so during an incident those actions queue rather than apply. Nothing is removed from a device and nobody is locked out of their laptop. The queued actions generally deliver once the component recovers.

How we measure this

  • We request Rippling's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Rippling publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Rippling goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required