iClassPro 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 iClassPro Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Connectivity IssueThis incident has been resolved. Following the deployed fix, system performance has remained stable and the metrics we have been monitoring have returned to normal levels. Users should no longer experience intermittent… | 2h 25m | Resolved |
| Sep 3, 2026 | Application Issue Impacting Some CustomersThis incident has been resolved. | 7h 59m | Resolved |
| Mar 20, 2026 | Staff Email VerificationOur development team has implemented a fix, and the issue has now been resolved. We appreciate your patience while we worked to address this issue. If you have any questions, please don’t hesitate to contact our support… | 9h 16m | Resolved |
| Mar 13, 2026 | Increased Login Prompts for StaffOur development team has implemented a fix, and the issue has now been resolved. We appreciate your patience while we worked to address this issue. If you have any questions, please don’t hesitate to contact our support… | 15h 48m | 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 iClassPro 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 iClassPro 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 iClassPro 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 iClassPro outage in this window ran 15h 48m, against a mean recovery of 8h 52m. If you depend on iClassPro 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.