Skip to main content

Is HackerRank Down?

No — HackerRank is up

Reachable from all 8 checked regions

Average response time: 624ms

Last checked · checks run every 6 hours

Official status page: https://status.hackerrank.com

HackerRank uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
468ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 60 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

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

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

lax
220ms
DNS 88ms TCP 1ms TLS 7ms TTFB 218ms
lhr
248ms
DNS 90ms TCP 2ms TLS 6ms TTFB 246ms
nrt
593ms
DNS 296ms TCP 1ms TLS 4ms TTFB 592ms
ord
337ms
DNS 160ms TCP 1ms TLS 5ms TTFB 336ms
sin
1471ms
DNS 605ms TCP 201ms TLS 205ms TTFB 1414ms
sjc
306ms
DNS 183ms TCP 1ms TLS 6ms TTFB 304ms
syd
1507ms
DNS 387ms TCP 0ms TLS 6ms TTFB 1506ms
yyz
313ms
DNS 195ms TCP 13ms TLS 27ms TTFB 302ms

What HackerRank does

HackerRank is the platform companies use to screen and interview developers. Recruiters send coding assessments from inside their applicant tracking system and get results scored automatically, and the Interview product runs live technical interviews in a shared editor. Because it sits inside a hiring pipeline, an outage lands on a candidate mid-test and an interviewer with a scheduled call, not just on an internal team.

What an outage looks like

A test will not open from the invitation link, or opens and then fails to submit at the end. The code editor stops accepting input or loses its connection mid-question, and the run and compile step hangs without returning results. Live interviews fail to start or drop the shared editor. Recruiters find that assessment invitations sent from an ATS integration never reach candidates.

What to do about it

Check HackerRank's Service Health Dashboard at status.hackerrank.com, then the per-region measurements here. If you are a candidate mid-assessment, screenshot the failure with a visible clock and email the recruiter immediately rather than restarting the test, because a retry can consume an attempt. If you are the recruiter, reschedule rather than letting a candidate work through a degraded editor, since the score will not be representative.

Is it down for everyone, or just you?

If this page says HackerRank 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

HackerRank outage FAQ

Is HackerRank down for everyone or just me?
Compare status.hackerrank.com with the per-region measurements on this page. A failure visible from several of our regions at once points at the platform. If those look clean, the usual local causes are a corporate network blocking the editor's connection, a browser extension interfering with the code editor, or a proctored test refusing to run under a restrictive VPN.
What happens to my test if HackerRank goes down mid-assessment?
Contact the recruiter before you do anything else, and do not close the tab if you can avoid it. Assessment timers and attempt limits are set by the company that sent the invitation rather than by HackerRank, so the recovery depends on them: many will reissue an invitation or extend the window, but a restarted test can count against a limited number of attempts.
Does a HackerRank outage affect scheduled live interviews?
The Interview product runs in the same platform as assessments, so a broad outage can take both. In practice interviews are easier to salvage: a shared editor can be replaced with screen sharing over whatever video tool the call already uses, and most interviewers keep the questions outside the platform. Agree a fallback with the candidate at the start rather than losing the slot.
Do assessment invitations sent during an outage still arrive?
Not reliably. Invitations sent through an applicant tracking system integration depend on the platform accepting the request, so an outage can leave a recruiter believing a candidate was invited when nothing was sent. After an outage clears, check the assessment list in HackerRank rather than trusting the ATS record, and resend anything that shows no invitation.

How we measure this

  • We request HackerRank's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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. We only change the 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 HackerRank publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when HackerRank goes down

This page refreshes every 6 hours. 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