Rise People Outage History
4 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Rise People Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 13, 2026 | Email delivery delayThis incident has been resolved. All unsent messages have now been sent. | 2h 42m | Resolved |
| May 12, 2026 | Latency in Payroll systemsService levels have returned to normal. | 6h 18m | Resolved |
| Apr 27, 2026 | Login failureThis issue has been resolved. Normal service is restored. | 2h 8m | Resolved |
| Jan 6, 2026 | Desktop and mobile outageThe issue has been identified and resolved. Our teams are continuing to monitor but we do not expect a recurrence. | 2 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Rise People incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Rise People Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Rise People acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Rise People outage in this window ran 6h 18m, against a mean recovery of 2h 48m. If you depend on Rise People in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.