Time-ordered UUID version 7
03UUIDv7 begins with a 48-bit Unix-epoch millisecond timestamp.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 5.7 ↗
RFC 9562 · § 5.7EXAMPLE
3 / 3
03
Compare ordered prefixes
Different millisecond prefixes sort by time; same-millisecond order depends on generation choices.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
The remaining 74 non-layout bits hold randomness and optionally supported monotonicity subfields.
- The remaining 74 non-layout bits hold randomness and optionally supported monotonicity subfields.
- Multiple identifiers in one millisecond need careful generation state.
- A sortable timestamp is not a globally guaranteed creation order.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy