UUIDv7 doesn't have the properties you think it does
Web page · https://alexsci.com/blog/uuidv7-is-weird
First seen by Oriel on .
AI summary
The post argues that UUIDv7 guarantees uniqueness but does not strictly guarantee accurate timestamps, monotonic ordering, or unguessability; those properties depend on implementation choices and system conditions.
- RFC 9562 permits generators to alter timestamps, so the embedded time may differ substantially from when an ID was generated.
- Python's uuid.uuid7() can advance its timestamp without bound under load after the system clock moves backwards, according to the author's example.
- UUIDv7 IDs can reveal high-precision creation-time metadata, though the author describes this as a concern only in some contexts.
- Clock synchronization prevents strict ordering across nodes, and implementations without counters can produce out-of-order IDs even on one node.
- The author recommends evaluating each implementation's guarantees, operating limits, clock assumptions, timestamp behavior, and ID guessability.
#uuidv7 #distributed systems #time synchronization #security
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Hacker News: 182, latest observation ; +160 over observed period since
- Lobsters: 45, latest observation ; +44 over observed period since
Comments
Comment count reported by the source.
- Hacker News: 160, latest observation ; +156 over observed period since
- Lobsters: 12, latest observation ; +12 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Hacker News | 50211746 | https://alexsci.com/blog/uuidv7-is-weird/ Read discussion |
| Lobsters | kcyzco | https://alexsci.com/blog/uuidv7-is-weird/ Read discussion |