Respondus Outage History
2 incidents recorded over the last 365 days, 2 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 Respondus Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 30, 2026 | Respondus Monitor Service NoticeRespondus Monitor continues to function normally. No further updates will be provided. | 1h 36m | Resolved |
| Feb 19, 2026 | LockDown Browser (Mac and iPad) Failing to Launch with Canvas New QuizzesInstructure has deployed a hotfix that resolves the issue causing LockDown Browser for Mac and iPad to fail when launching Canvas New Quizzes. | 8h 27m | 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 Respondus 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 Respondus 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 Respondus 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 Respondus outage in this window ran 8h 27m, against a mean recovery of 5h 2m. If you depend on Respondus 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.