Rippling outage on 14 November 2026

Problem reports about Rippling rose to outage level at 14:47 Central European time on Saturday 14 November 2026 and stayed there for 1 h 45 min.

They peaked at 120 reports in 15 minutes at 15:03, at a time of day when there are usually almost none, and 344 reports came in while the outage lasted.

12 other services had an outage spike at the same time.

Is Rippling down right now?

Started

14:47

Sat 14 Nov, Central European time

At outage level

1 h 45 min

Ended 16:32

Busiest 15 minutes

120

reports, at 15:03

Reports during the outage

344

Counted in 15-minute windows

Timeline

Reports from Sat 08:45 to Sat 19:45

One bar per 15 minutes, Central European time. Red bars are the outage; the dashed line is what a usual day sees at that time.

Same time

Other services with an outage at the same time

Their reports also reached outage level while Rippling's did. Many services failing together can point to a shared cause, such as a network or cloud provider, but reports alone cannot show it.

Outage
Microsoft Outlook
Thu 17:42–19:47

131,553peak reports
Outage
Microsoft 365
Thu 17:59–19:47

48,448peak reports
Outage
Microsoft Store
Thu 18:27–19:47

11,786peak reports
Outage
Workday
Fri 19:08–19:47

2,977peak reports
Outage
911
Thu 23:04–19:47

1,123peak reports
Outage
Bradesco
13:02–17:17

417peak reports
Outage
Pix
13:17–19:02

212peak reports
Outage
Iliad
06:47–16:32

150peak reports
Outage
ZDF
13:32–19:47

123peak reports
Outage
Marriott
12:02–19:47

111peak reports
Outage
1&1
06:02–17:47

109peak reports
Outage
My Social Security
14:17–16:32

95peak reports

Rippling: live status and other outages

Check whether Rippling is down right now: the live page shows the last 24 hours and fixes to try.

November 2026 outage report All recent outages

Embed

Put this outage in an article

Copy a frame with the chart and numbers above, or an image of the same card for places that do not allow frames, such as newsletters. Both link back to this page. More for journalists.

<iframe src="https://isitdownrightnow.app/embed/rippling/2026-11-14/" title="Rippling outage on 14 November 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe>
<p><a href="https://isitdownrightnow.app/services/rippling/outages/2026-11-14/">Rippling outage on 14 November 2026</a> from IsItDownRightNow.app</p>

Frame: the chart and numbers, as a small card

<a href="https://isitdownrightnow.app/services/rippling/outages/2026-11-14/"><img src="https://isitdownrightnow.app/share/rippling/2026-11-14.png" alt="Rippling outage on 14 November 2026: problem reports over time" width="600" height="315" loading="lazy"></a>

Image: the same card as a picture

[![Rippling outage on 14 November 2026](https://isitdownrightnow.app/share/rippling/2026-11-14.png)](https://isitdownrightnow.app/services/rippling/outages/2026-11-14/)

Markdown: the image, for README files and forums

Where these numbers come from

The numbers are problem reports that users sent to a public outage-reporting service, counted in 15-minute windows and kept as this site's live page showed them. A spike counts as an outage when reports are more than twice the usual level and far above the day's average. Reports show that many people had trouble at the same time, not what caused it; the service's own status page is the place for that.