Top Hat Outage History
18 incidents recorded over the last 365 days, 8 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 Top Hat Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Some question functionality unavailableQuestion functionality in the application has now been restored. | 6h 9m | Resolved |
| Oct 29, 2026 | Scheduled MaintenanceMaintenance has concluded and core system components are operational. Some math problem sets and interactive math questions remain temporarily unavailable. | 18h 0m | Scheduled |
| Oct 22, 2026 | Security Update: Top Hat & Aktiv Unaffected by Recent PHP VulnerabilitiesWe are tracking the critical PHP vulnerabilities disclosed on October 21, 2026. Our main Top Hat and Aktiv applications are not affected. We will continue to monitor developments and share updates as needed. | 0 min | Resolved |
| Aug 26, 2026 | Investigating Gradebook Access IssuesSystem performance has remained stable post-fix, and this incident is now closed. | 2h 19m | Resolved |
| Aug 5, 2026 | Failure to Load Message Appearing for Some UsersIssue has been fixed and access to Top Hat has been restored. | 30 min | Resolved |
| Aug 2, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| Jul 5, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| Jun 29, 2026 | Scheduled Maintenance: Canadian Server MigrationThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Jun 21, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| Jun 7, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| May 24, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| Mar 29, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| Mar 27, 2026 | Critical Service Disruption on US ServerThis incident has been resolved. | 3h 26m | Resolved |
| Jan 18, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| Dec 7, 2025 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Dec 1, 2025 | Question Submission ErrorsBeginning December 1, some students encountered errors when attempting to submit answers. Clearing cache and cookies resolved the issue for many multiple-choice questions, while some algorithmic questions continued to… | 0 min | Resolved |
| Nov 28, 2025 | Aktiv Assignment Loading and Submission IssuesStarting Friday afternoon, students reported that Aktiv assignments were not loading and were instead seeing a consistent error message across multiple courses. Only assignments that were currently active or due were… | 0 min | Resolved |
| Nov 25, 2025 | LaTeX Display IssueBetween November 25 and November 30, some questions containing LaTeX did not display correctly or failed to appear for students. This issue has now been fully resolved. Ungraded questions and newly added questions will… | 0 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 Top Hat 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 Top Hat 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 Top Hat 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 Top Hat outage in this window ran 18h, against a mean recovery of 4h 1m. If you depend on Top Hat 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.