International
The Morning Dev

Only the news worth knowing

‹
 

Outage · High impact

The rate limiter that checked the database first: how rejected requests kept 2,100 students out of their exams

DEV · By Kashif Manzer ·

The Brief

  • On Tuesday 21 October 2026 at about 12:18, exams were due to start at several schools and colleges, and students could not open them.
  • The start button did nothing or the page never loaded, according to the source.
  • Three institutions were affected, with up to 2,100 students locked out.

Why it matters

A rate limiter that queries the database before rejecting requests can add load exactly when traffic spikes, so the limiter itself can cause the outage it was meant to prevent.

Who’s affected

  • Backend teams using database-backed rate limiting
  • Operators of systems with time-critical traffic spikes such as exam start times

On Tuesday 21 October 2026, at 12:18 in the afternoon, exams were about to start at several schools and colleges. Students sat down, opened their exam, and nothing happened. The start button did nothing, or the page never loaded. Three institutions were affected, up to 2,100…

Timeline

  1. Students at three institutions could not start exams around 12:18, with up to 2,100 affected

  2. DEV Community: backend

    The rate limiter that checked the database first: how rejected requests kept 2,100 students out of their exams

How do you feel about this?

0 Comments

    The rate limiter that checked the database first: how rejected requests kept 2,100 students out of their exams – The Morning Dev