Riipen Outage History
5 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 Riipen Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 13, 2026 | Platform OutageThis incident has been resolved. | 1h 59m | Resolved |
| Aug 23, 2026 | Infrastructure upgradeWe will be undergoing scheduled maintenance at this time and expect downtime for 1-5 minutes. | 5 min | Scheduled |
| Apr 9, 2026 | Performance DegredationThis incident has been resolved. | 2h 47m | Resolved |
| Jan 6, 2026 | Email outageThis incident has been resolved. | 57 min | Resolved |
| Nov 12, 2025 | Question and answers loadingThis incident has been resolved. | 16 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 Riipen 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 Riipen 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 Riipen 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 Riipen outage in this window ran 2h 47m, against a mean recovery of 1h 13m. If you depend on Riipen 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.