- Service Status
- /
- Respondus LockDown Browser

Is Respondus LockDown Browser Down?
- Respondus LockDown Browser's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 218 ms
Right now
The verdict is the worse of these two. How we decide
Respondus LockDown Browser's status page
status.respondus.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| LockDown Browser | Operational |
| Respondus Monitor (webcam) | Operational |
| StudyMate Campus | Operational |
FlareWarden checks
web.respondus.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 218 ms
- Checked
By region
- Amsterdam reachable, 126 ms
- Dallas reachable, 174 ms
- Paris reachable, 121 ms
- San Jose reachable, 115 ms
- Singapore reachable, 413 ms
- Stockholm reachable, 165 ms
- Sydney reachable, 319 ms
- Toronto reachable, 314 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 75 ms | 3 ms | 9 ms | 126 ms |
| Dallas | 134 ms | 1 ms | 17 ms | 173 ms |
| Paris | 79 ms | 2 ms | 9 ms | 121 ms |
| San Jose | 66 ms | 2 ms | 14 ms | 114 ms |
| Singapore | 377 ms | 2 ms | 10 ms | 413 ms |
| Stockholm | 80 ms | 16 ms | 21 ms | 160 ms |
| Sydney | 28 ms | 1 ms | 39 ms | 319 ms |
| Toronto | 164 ms | 1 ms | 13 ms | 312 ms |
History
Incidents Respondus LockDown Browser reported
Since Oct 22, 28 days · from status.respondus.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Respondus LockDown Browser website availability
Measured by FlareWarden · web.respondus.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 255ms
Last 30 days
34-day clean streakMeasured by FlareWarden's own checks of web.respondus.com from multiple regions every 6 hours. Respondus LockDown Browser's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 34 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Respondus LockDown Browser does
Respondus LockDown Browser is a custom browser that locks down a computer or tablet while a student sits an online exam inside a learning management system such as Canvas, Blackboard, Brightspace or Moodle. Respondus says over 2,000 higher education institutions use it. Respondus Monitor builds on it, recording students through a webcam for automated proctoring, so both stand between a student and a timed test.
What an outage looks like
Respondus Monitor sessions fail to start, or the pre-exam webcam steps crawl or end on a gateway error. LockDown Browser reports 'Unable to connect to Respondus Server' or 'Error sending exam start notification', and instructors cannot open the LockDown Browser Dashboard. In February 2026 a Canvas New Quizzes fault left the iPad app on a blank screen and the Mac app on error code -379.
What to do about it
Check status.respondus.com, which lists LockDown Browser, Respondus Monitor (webcam) and StudyMate Campus as separate rows, then your LMS status page, because a Canvas or Blackboard failure blocks the exam too. When only Mac and iPad failed, Respondus named Windows and Chromebook as a temporary workaround. Tell your instructor before the deadline, with a screenshot of the error and the time it appeared.
Is it down for everyone, or just you?
If this page says Respondus LockDown Browser 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
Respondus LockDown Browser outage FAQ
Is LockDown Browser down for everyone or just me?
Will I lose my answers if LockDown Browser loses connection?
Does a Canvas or AWS outage affect LockDown Browser?
How long do Respondus outages usually last?
Who should I contact when LockDown Browser fails during an exam?
How we measure this
- We request Respondus LockDown Browser'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 Respondus LockDown Browser 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 Respondus LockDown Browser 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 Respondus LockDown Browser goes down
We check Respondus LockDown Browser 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
