Vendor reports: major outageResolved · vendor status “resolved”Official status API

Issues using job codes and dimensions in Time and Attendance and Payroll

Reported by Rippling · HR, Finance & Ops · source last read 11 min ago

Official source (opens in a new tab)
Vendor start
Nov 24, 2025, 20:13 UTC
Vendor's clock
Resolved
Nov 25, 2025, 08:25 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
12 h 12 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Rippling reports major outage: "Issues using job codes and dimensions in Time and Attendance and Payroll".[E1, E2]
  • The vendor marked it resolved at 2025-11-25 08:25 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-11-25 08:25 UTC · summary s1, evidence d1597b07a2812a72

Evidence (7)
  1. E1Rippling reports major outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Issues using job codes and dimensions in Time and Attendance and Payroll". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-11-24 20:13 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2025-11-25 08:25 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Rippling is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Nov 24, 2025, 20:13 UTCVendor-reported startVendor time
  2. Nov 25, 2025, 08:25 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.