Is Top Hat Down?
- Top Hat's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 233 ms
Right now
The verdict is the worse of these two. How we decide
Top Hat's status page
status.tophat.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Top Hat API | Operational |
| Aktiv API | Operational |
FlareWarden checks
tophat.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 233 ms
- Checked
By region
- Amsterdam reachable, 77 ms
- Chicago reachable, 136 ms
- London reachable, 220 ms
- San Jose reachable, 86 ms
- Singapore reachable, 491 ms
- Sydney reachable, 582 ms
- Tokyo reachable, 126 ms
- Toronto reachable, 152 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 47 ms | 2 ms | 6 ms | 70 ms |
| Chicago | 119 ms | 1 ms | 3 ms | 130 ms |
| London | 52 ms | 2 ms | 5 ms | 211 ms |
| San Jose | 73 ms | 2 ms | 4 ms | 83 ms |
| Singapore | 164 ms | 1 ms | 4 ms | 484 ms |
| Sydney | 9 ms | 1 ms | 3 ms | 580 ms |
| Tokyo | 112 ms | 1 ms | 4 ms | 122 ms |
| Toronto | 84 ms | 8 ms | 12 ms | 132 ms |
History
Incidents Top Hat reported
Since Oct 22, 13 days · from status.tophat.com
- Incidents
- 1
- Major or critical
- 1
- Median to resolve
- 6h 9m
- lasted 6h 9m
Top Hat website availability
Measured by FlareWarden · tophat.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 227ms
Last 30 days
14-day clean streakMeasured by FlareWarden's own checks of tophat.com from multiple regions every 6 hours. Top Hat's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 14 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Top Hat does
Top Hat is a student engagement platform for colleges and universities. Instructors present slides, ask in-class questions, take attendance and run assignments and tests, and students answer in a browser at app.tophat.com or in the Top Hat mobile app. Top Hat says more than 30,000 instructors at over 1,200 institutions use it, and it integrates with Canvas, Blackboard, D2L Brightspace, Moodle and Sakai.
What an outage looks like
Pages show a 'Top Hat failed to load' error, course content or the Gradebook will not open, or students get errors submitting answers. When Top Hat's real-time service fails, presenting slides and viewing student responses stop working mid-class. Grades can lag: during the October 2025 Gradebook incident submissions were queued and grades, attendance included, appeared hours later. Course invitation and verification emails can also stall.
What to do about it
Check status.tophat.com, which has separate rows for the Top Hat API and the Aktiv API. During the October 2025 AWS outage Top Hat advised postponing tests, exams and gradebook work until it was resolved, so instructors should consider moving a timed assessment. If answers will not submit, Top Hat found that clearing cache and cookies fixed many cases in December 2025. Account problems go to support.tophat.com.
Is it down for everyone, or just you?
If this page says Top Hat is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Top Hat outage FAQ
Is Top Hat down for everyone or just me?
Will my Top Hat answers and attendance be lost during an outage?
Does an AWS or Google Cloud outage affect Top Hat?
Does Top Hat work when Canvas or my LMS is down?
Does the check on this page measure the Top Hat app?
How we measure this
- We request Top Hat's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Top Hat publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Top Hat itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Top Hat goes down
We check Top Hat every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring