# New connections failed, old ones worked: the failover that sent writes to a read-only database

Source: [DEV Community: backend](https://dev.to/kashif_manzer/new-connections-failed-old-ones-worked-the-failover-that-sent-writes-to-a-read-only-database-m5b) · 2026-11-15 · Backend
Page: https://themorning.dev/story/new-connections-failed-old-ones-worked-the-failover-that-sent-writes-to-a-read-o-d16401b00ecd758e
Kind: outage · Impact: medium

## In brief

- On 28 October 2026 the RIPE Database began failing some updates while others succeeded.
- Failed requests were refused, and the failure was not visible from outside the service.
- The cause as described is a failover that sent writes to a read-only database.

## Why it matters

Teams relying on database writes during failovers can see intermittent, hard-to-predict failures when some connections are routed to a read-only node while others are not.

## Timeline

- 2026-10-28: RIPE Database began failing some updates after a failover sent writes to a read-only database
- 2026-11-15: DEV Community article describing the incident was published

## Coverage

- [New connections failed, old ones worked: the failover that sent writes to a read-only database](https://dev.to/kashif_manzer/new-connections-failed-old-ones-worked-the-failover-that-sent-writes-to-a-read-only-database-m5b) — DEV Community: backend, 2026-11-15

Tags: failover, database, read-only, incident, ripe

---

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
