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

Source: [DEV Community: backend](https://dev.to/kashif_manzer/the-rate-limiter-that-checked-the-database-first-how-rejected-requests-kept-2100-students-out-of-4ndj) · 2026-11-18 · Backend
Page: https://themorning.dev/story/the-rate-limiter-that-checked-the-database-first-how-rejected-requests-kept-2-10-c83a8d3bc5e632a7
Kind: outage · Impact: high

## In 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.

## Timeline

- 2026-10-21: Students at three institutions could not start exams around 12:18, with up to 2,100 affected

## Coverage

- [The rate limiter that checked the database first: how rejected requests kept 2,100 students out of their exams](https://dev.to/kashif_manzer/the-rate-limiter-that-checked-the-database-first-how-rejected-requests-kept-2100-students-out-of-4ndj) — DEV Community: backend, 2026-11-18

Tags: rate-limiting, databases, incident, backend, reliability

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
