RiversideFM Outage History
12 incidents recorded over the last 365 days, 12 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 RiversideFM Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | Working on a ResolutionThe issue causing exports to take too long to complete has been resolved, please let us know if you experience any further issues. | 37 min | Resolved |
| Oct 28, 2026 | Working on a ResolutionThis incident has been resolved. | 2h 55m | Resolved |
| Jun 17, 2026 | Unable to Record in StudioThis incident has been resolved. | 9 min | Resolved |
| Jun 17, 2026 | Issue InvestigationThe issue with starting the recording has been resolved, please let us know if you experience any further issues. | 8 min | Resolved |
| Mar 31, 2026 | Issue with accessing the project pageThis incident has been resolved. | 55 min | Resolved |
| Mar 31, 2026 | Issue with connecting to the studioThe issue with connecting to the studio has been resolved, please let us know if you experience any further issues. | 1h 24m | Resolved |
| Mar 25, 2026 | Editor exports taking longerThe issue with the Editor taking longer to export has been resolved. Please let us know if you experience any further issues. | 3h 9m | Resolved |
| Feb 5, 2026 | Transcriptions processingThe issue with Transcriptions has been resolved, please let us know if you experience any further issues. | 8h 2m | Resolved |
| Feb 5, 2026 | Working on a ResolutionThis incident has been resolved. | 9h 3m | Resolved |
| Dec 18, 2025 | Lobby IssueThe issue with joining the studio from the lobby has been resolved, please let us know if you experience any further issues. | 1h 17m | Resolved |
| Nov 17, 2025 | Clips taking longer to exportThe issue with slower clip exports has been resolved, please let us know if you experience any further issues. | 4h 47m | Resolved |
| Nov 6, 2025 | Issue InvestigationThis incident has been resolved. | 6 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 RiversideFM 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 RiversideFM 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 RiversideFM 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 RiversideFM outage in this window ran 9h 3m, against a mean recovery of 2h 43m. If you depend on RiversideFM 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.