Skip to main content
Rippling logo

Is Rippling Down?

No — Rippling is up
Rippling's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 380 ms

Right now

The verdict is the worse of these two. How we decide

Rippling's status page

status.rippling.com · read · checked every 3 minutes

Operational
Rippling's components, as its status page reports them
ComponentStatus
Rippling AppOperational
Single Sign-on (SSO)Operational
AuthenticationOperational
RPassOperational
VLDAPOperational
Platform APIOperational
Third-party integrationsOperational
RADIUSOperational
Devices appOperational
Workflow StudioOperational
NotificationsOperational
Rippling AIOperational
8 more, all operational · show all 20
All of Rippling's components
ComponentStatus
Rippling AppOperational
Identity & App Management
Single Sign-on (SSO)Operational
AuthenticationOperational
RPassOperational
VLDAPOperational
Platform APIOperational
Third-party integrationsOperational
RADIUSOperational
Device & Inventory Management
Devices appOperational
Platform Tools
Workflow StudioOperational
NotificationsOperational
Rippling AIOperational
Data
Reports & DashboardsOperational
PipelinesOperational
TransformationsOperational
Payroll
PayrollOperational
Benefits
BenefitsOperational
Time
TimesheetsOperational
SchedulingOperational
Rippling AI
Rippling AIOperational

FlareWarden checks

rippling.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
380 ms
Checked

By region

  • Ashburn reachable, 207 ms
  • Chicago reachable, 280 ms
  • Frankfurt reachable, 276 ms
  • Johannesburg reachable, 263 ms
  • London reachable, 854 ms
  • Los Angeles reachable, 158 ms
  • São Paulo reachable, 356 ms
  • Tokyo reachable, 651 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn101 ms1 ms8 ms162 ms
Chicago138 ms1 ms23 ms245 ms
Frankfurt33 ms4 ms6 ms149 ms
Johannesburg16 ms0 ms63 ms164 ms
London66 ms21 ms20 ms824 ms
Los Angeles41 ms2 ms27 ms118 ms
São Paulo248 ms1 ms5 ms335 ms
Tokyo241 ms1 ms8 ms628 ms
We check that rippling.com loads, not every feature behind it. Test it yourself

History

Incidents Rippling reported

Since Oct 22, 15 days · from status.rippling.com

Incidents
3
Major or critical
1
Median to resolve
1h 25m
  1. lasted 1h 25m
  2. lasted 10h 53m
  3. Rippling AI is down

    major ·

    lasted 11m

Rippling website availability

Measured by FlareWarden · rippling.com

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

Last 30 days

30-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 32 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 31 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of rippling.com from multiple regions every 6 hours. Rippling's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 89 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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 the verdict is the worse of what it reports and what our checks see: a major outage of Rippling itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Rippling goes down

We check Rippling every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required