Skip to main content
Respondus LockDown Browser logo

Is Respondus LockDown Browser Down?

No — Respondus LockDown Browser is up
Respondus LockDown Browser's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 166 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

Operational
Respondus LockDown Browser's components, as its status page reports them
ComponentStatus
LockDown BrowserOperational
Respondus Monitor (webcam)Operational
StudyMate CampusOperational

FlareWarden checks

web.respondus.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
166 ms
Checked

By region

  • Amsterdam reachable, 117 ms
  • Dallas reachable, 100 ms
  • Newark reachable, 117 ms
  • Paris reachable, 84 ms
  • San Jose reachable, 94 ms
  • Stockholm reachable, 259 ms
  • Sydney reachable, 350 ms
  • Toronto reachable, 213 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam36 ms2 ms15 ms115 ms
Dallas68 ms1 ms10 ms99 ms
Newark85 ms2 ms8 ms116 ms
Paris39 ms2 ms8 ms84 ms
San Jose63 ms2 ms8 ms92 ms
Stockholm56 ms16 ms24 ms255 ms
Sydney122 ms1 ms6 ms350 ms
Toronto131 ms1 ms8 ms211 ms
We check that web.respondus.com loads, not every feature behind it. Test it yourself

History

Incidents Respondus LockDown Browser reported

Since Oct 22, 32 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

38-day clean streak
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 31 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Nov 6: 100.00% uptime, 32 checks
Nov 7: 100.00% uptime, 32 checks
Nov 8: 100.00% uptime, 32 checks
Nov 9: 100.00% uptime, 32 checks
Nov 10: 100.00% uptime, 32 checks
Nov 11: 100.00% uptime, 32 checks
Nov 12: 100.00% uptime, 32 checks
Nov 13: 100.00% uptime, 32 checks
Nov 14: 100.00% uptime, 32 checks
Nov 15: 100.00% uptime, 32 checks
Nov 16: 100.00% uptime, 32 checks
Nov 17: 100.00% uptime, 32 checks
Nov 18: 100.00% uptime, 32 checks
Nov 19: 100.00% uptime, 32 checks
Nov 20: 100.00% uptime, 32 checks
Nov 21: 100.00% uptime, 32 checks
Nov 22: 100.00% uptime, 24 checks
Oct 24 Today
No downtime Partial Downtime Not measurable No data

Measured 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 — 38 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.

Test it yourself

Related services

Respondus LockDown Browser outage FAQ

Is LockDown Browser down for everyone or just me?
Usually just you, unless status.respondus.com shows an incident. Respondus says error codes such as -7, -21, -105, -106 and -118, often with 'Failed to load page. Please check network connection', point to the network rather than LockDown Browser, and suggests another network. Antivirus or firewall software and a wrong computer clock also block it. The check on this page loads web.respondus.com, the Respondus website, not the exam servers.
Will I lose my answers if LockDown Browser loses connection?
Usually not, because your school's learning system saves the answers, not LockDown Browser. Respondus says a blank screen typically means lost connectivity to your institution's server, and that after restarting LockDown Browser you can normally pick up where you left off, if the LMS permits a return. With Respondus Monitor you repeat the webcam check, and a brief drop leaves a noted gap in the video.
Does a Canvas or AWS outage affect LockDown Browser?
Yes, because exams launch from the learning system and Respondus Monitor runs on AWS. In October 2025 Respondus reported that an AWS incident stopped many students launching exams from their LMS. The February 2026 Mac and iPad launch failure was fixed by an Instructure hotfix, and in May 2026 an Instructure developer key rotation broke the LockDown Browser Dashboard for Canvas instructors.
How long do Respondus outages usually last?
Usually a few hours at most. Incidents on status.respondus.com since 2024 range from an 11-minute Respondus Monitor slowdown in September 2025 to a March 2025 AWS-related problem that degraded Monitor and took Chromebook users of LockDown Browser offline for about four hours. The February 2026 Canvas New Quizzes fault on Mac and iPad took about eight and a half hours to fix.
Who should I contact when LockDown Browser fails during an exam?
Your instructor first, then your school's help desk, because they control exam settings, deadlines and the download link for your institution. Respondus lists the Help Center inside LockDown Browser, a student knowledge base, an online support request form and live chat for Respondus Monitor. Respondus says tickets generally get a reply within 24 hours, excluding weekends and US holidays, so a ticket will not rescue a deadline.

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 403 or 429 means 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
Free plan available No credit card required