Snowflake ID Examples - Real Twitter, Discord & Instagram IDs Explained

Key Properties of Snowflake IDs

• 64-bit integers — fit in a standard database BIGINT column
• Time-ordered — sorting by ID gives chronological order
• Distributed — generated independently on each server
• No coordination needed — no central counter or database
• Timestamp embedded — creation time extractable from ID alone
• High throughput — 4,096 IDs per millisecond per worker

Use the TechConverter Snowflake Decoder to decode any Snowflake ID interactively.

// Universal Snowflake Decoder
function decodeSnowflake(id, epoch) {
  const snowflake = BigInt(id);
  const timestamp = Number((snowflake >> 22n) + BigInt(epoch));
  const workerId = Number((snowflake >> 17n) & 0x1Fn);
  const datacenterId = Number((snowflake >> 12n) & 0x1Fn);
  const sequence = Number(snowflake & 0xFFFn);
  
  return {
    id: id,
    timestamp: timestamp,
    date: new Date(timestamp),
    workerId: workerId,
    datacenterId: datacenterId,
    sequence: sequence
  };
}

// Examples
const TWITTER_EPOCH = 1288834974657;
const DISCORD_EPOCH = 1420070400000;

// Decode Twitter ID
const twitter = decodeSnowflake('1382350606417817604', TWITTER_EPOCH);
console.log('Twitter:', twitter.date.toUTCString());
// Output: Wed, 14 Apr 2021 15:30:06 GMT

// Decode Discord ID
const discord = decodeSnowflake('175928847299117063', DISCORD_EPOCH);
console.log('Discord:', discord.date.toUTCString());
// Output: Sat, 30 Apr 2016 11:18:25 GMT

# Python Snowflake Decoder
from datetime import datetime

def decode_snowflake(snowflake_id, epoch):
    snowflake = int(snowflake_id)
    timestamp = ((snowflake >> 22) + epoch) / 1000
    worker_id = (snowflake >> 17) & 0x1F
    datacenter_id = (snowflake >> 12) & 0x1F
    sequence = snowflake & 0xFFF
    
    return {
        'id': snowflake_id,
        'timestamp': timestamp,
        'date': datetime.fromtimestamp(timestamp),
        'worker_id': worker_id,
        'datacenter_id': datacenter_id,
        'sequence': sequence
    }

# Examples
TWITTER_EPOCH = 1288834974657
DISCORD_EPOCH = 1420070400000

# Decode Twitter ID
twitter = decode_snowflake('1382350606417817604', TWITTER_EPOCH)
print(f"Twitter: {twitter['date']}")
# Output: 2021-04-14 15:30:06.657000

# Decode Discord ID
discord = decode_snowflake('175928847299117063', DISCORD_EPOCH)
print(f"Discord: {discord['date']}")
# Output: 2016-04-30 11:18:25.796000

Common Snowflake ID Patterns

• Sequential IDs: IDs generated close together have similar values (e.g., 1382350606417817604, 1382350606417817605)
• Time-ordered: Larger IDs are always newer than smaller IDs
• Unique globally: No two IDs are ever the same across all servers
• Sortable: Can be sorted chronologically by numeric value
• Compact: 64-bit integers are smaller than UUIDs (128-bit)

Real-World Use Cases for Snowflake ID Examples

Forensic Analysis

Use example IDs to verify timestamps in legal cases or investigations

Data Analysis

Analyze posting patterns and activity timelines using ID timestamps

Bot Development

Test ID generation and decoding logic with known examples

Learning

Understand distributed ID systems through real-world examples

Frequently Asked Questions

Q: Are these real Snowflake IDs?

A: Yes! All examples on this page are real IDs from Twitter, Discord, and Instagram that you can decode and verify.

Q: Can I use these IDs in my application?

A: These are examples for learning. Generate your own IDs using our Snowflake ID generator for production use.

Q: How do I generate my own Snowflake IDs?

A: Use our Twitter Snowflake ID Generator tool to create unique IDs following the same format as these examples.

Snowflake ID: 1382350606417817604

Binary (64 bits):
0001001100101001001001001001001001001001001001001001001000000100

Decoded:
  Timestamp bits (22-62): 329847756289
  + Twitter epoch:        329847756289 + 1288834974657 = 1618682730946 ms
  Created at:             2021-04-17 18:25:30.946 UTC

  Datacenter ID (bits 17-21): 0 (datacenter 0)
  Worker ID (bits 12-16):     1 (worker 1)
  Sequence (bits 0-11):       4

This tweet was posted on April 17, 2021 at 6:25 PM UTC.

Snowflake ID: 175928847299117063

Discord epoch: 1420070400000 ms (2015-01-01 00:00:00 UTC)

Decoded:
  Timestamp bits >> 22: 41943040
  + Discord epoch:      41943040 + 1420070400000 = 1420112343040 ms
  Created at:           2015-01-01 11:39:03.040 UTC

  Worker ID (bits 17-21): 0
  Process ID (bits 12-16): 0
  Sequence (bits 0-11): 7

This Discord entity was created on January 1, 2015 —
very early in Discord's history (Discord launched in 2015).

Standard Snowflake ID layout (Twitter format):

 63      22 21    17 16    12 11       0
 ┌────────┬──────┬──────┬────────────┐
 │  time  │ dcid │ wkid │  sequence  │
 │ 41 bits│5 bits│5 bits│  12 bits   │
 └────────┴──────┴──────┴────────────┘

 time:     milliseconds since epoch (41 bits = ~69 years)
 dcid:     datacenter ID (5 bits = 32 datacenters)
 wkid:     worker ID (5 bits = 32 workers per datacenter)
 sequence: counter within same millisecond (12 bits = 4096/ms)