All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Confirmed UUID v4 collision detected in production database

By

mittermayr

23d ago· 2 min readenNews

Summary

A developer reports a confirmed UUID v4 collision in their database, where a newly generated UUID matched one created a year ago. The collision was detected by a database constraint, ruling out a double-insert bug. The developer expresses shock and disbelief, noting the astronomical odds against such an event, and shares the specific UUID that collided (b6133fd6-70fe-4fe3-bed6-8ca8fc9386cd). They are using the popular 'uuid' npm package for generation.

Key quotes

· 3 pulled
I know what you're thinking... and I still can't believe it, but...
This morning, our database flagged a duplicate UUID (v4). I checked, thinking it may have been a double-insert bug or something, but no.
The original UUID was from a record added in 2025 (about a year ago), and today the system inserted a new document with a fresh UUIDv4 and it came up with the exact same one: b6133fd6-70fe-4fe3-bed6-8ca8fc9386cd
Snippet from the RSS feed
I know what you're thinking... and I still can't believe it, but...

You might also wanna read