Skip to listings

Study 02 · recomputed every read

Which of these platforms can actually be relied on?

Uptime here means the feed answered without an error, which is a lower bar than being useful: a source can answer perfectly and return nothing, and that is tracked separately for exactly that reason. The least reliable feed in the window is MyCareernet contests at 49%.

22

Feeds tracked

1,000

Reads recorded

23d

Window

100%

Median uptime

17/22

Feeds fully solid

5

With quiet failures

Sorted worst first solid ≥ 99% shaky 90-99% unreliable < 90%
  • MyCareernet contestsMyCareernet

    Unreliable49% answered

    42458ms median45 reads22 returned nothing (49%)last read 6h ago

    HTTP 503

  • HackerEarth challengesHackerEarth

    Unreliable54% answered

    1051ms median46 readslast read 6h ago

    HTTP 403

  • Internshala competitionsInternshala

    Unreliable89% answered

    3449ms median45 readslast read 6h ago

    every Internshala page failed: Error: HTTP 503

  • Devpost upcomingDevpost

    Shaky98% answered

    701ms median46 readslast read 6h ago

    HTTP 503

  • Devpost openDevpost

    Shaky98% answered

    634ms median46 readslast read 6h ago

    HTTP 503

  • Unstop competitionsUnstop

    Solid100% answered

    21056ms median46 readslast read 6h ago
  • Unstop hackathonsUnstop

    Solid100% answered

    7632ms median46 readslast read 6h ago
  • HackerRank contestsHackerRank

    Solid100% answered

    5118ms median45 reads4 returned nothing (9%)last read 6h ago
  • Unstop quizzesUnstop

    Solid100% answered

    2814ms median46 readslast read 6h ago
  • ETHGlobal eventsETHGlobal

    Solid100% answered

    2402ms median46 readslast read 6h ago
  • MLH season eventsMajor League Hacking

    Solid100% answered

    2149ms median46 reads41 returned nothing (89%)last read 6h ago
  • Hack Club

    Solid100% answered

    1993ms median46 readslast read 6h ago
  • Devfolio

    Solid100% answered

    1958ms median46 readslast read 6h ago
  • GeeksforGeeks contestsGeeksforGeeks

    Solid100% answered

    1323ms median45 reads45 returned nothing (100%)last read 6h ago
  • TechGig challengesTechGig

    Solid100% answered

    1144ms median45 readslast read 6h ago
  • lablab.ai AI hackathonslablab.ai

    Solid100% answered

    1052ms median45 readslast read 6h ago
  • Codeforces roundsCodeforces

    Solid100% answered

    962ms median45 readslast read 6h ago
  • LeetCode contestsLeetCode

    Solid100% answered

    910ms median45 readslast read 6h ago
  • CodinGame challengesCodinGame

    Solid100% answered

    905ms median45 reads45 returned nothing (100%)last read 6h ago
  • AtCoder contestsAtCoder

    Solid100% answered

    892ms median45 readslast read 6h ago
  • Kaggle competitionsKaggle

    Solid100% answered

    810ms median45 readslast read 6h ago
  • CodeChef contestsCodeChef

    Solid100% answered

    777ms median45 readslast read 6h ago

How to read this fairly

01

This measures our read, not their website

A feed failing for us does not mean the platform was down for students. It can mean a changed response shape, a rate limit aimed at us, or a network path that was having a bad day. It is a measure of how dependable that feed is to build on.

02

Answering and being useful are different columns

A source that returns an empty list has not failed: sometimes a platform genuinely has nothing open. The empty count is kept separate so a quiet breakage is visible instead of hiding behind a hundred percent.

03

Our own mistakes are in here

Some failures were bugs in our adapter rather than problems at the platform, and they are not filtered out. A reliability index that only ever indicted other people would not be worth reading.

04

Recent history only

The window is the most recent runs, so a source that broke months ago and was fixed does not look broken forever. The window length is printed at the top.

For anyone building on these feeds