How to read Bluesky network activity stats

Bluesky Stats used to answer one simple question: how many people are on Bluesky?

It still does that. It now also shows public activity from the network: posts and follows from the last hour, posts by recent hour, top languages, and top linked domains.

Use these numbers as network context. They tell you what the public network is doing. Your own Bluesky analytics still decide the posting plan.

What the stats page shows

The stats page has two layers.

The first layer is user growth:

• current Bluesky user count
• current estimated growth rate
• estimated new users per day

The second layer is public activity from Bluesky's event stream:

• posts observed in the last hour
• follow events in the last hour
• percentage of recent posts with images
• percentage of recent posts with links
• posts by recent hour
• top languages
• top linked domains

Those activity numbers come from public Bluesky events observed through the AT Protocol firehose/Jetstream path. Bluesky's own docs describe the firehose as an authenticated event stream for syncing updates such as posts, likes, follows, and handle changes. Jetstream is the simpler JSON streaming layer built for easier firehose consumption, with filtering by collection or repo.

The page reads public network events and aggregates them into counters instead of scraping timelines or guessing from samples.

How to use last-hour posts

Last-hour posts tell you how busy the public network is right now.

I would use this before posting something important. If the number is high, the network is active but the feed is crowded. If the number is low, there is less competition, but fewer people may be refreshing feeds.

Both cases need context.

Use it this way:

• For announcements, avoid judging one quiet hour as failure.
• For live events, look for activity rising before you post.
• For scheduled posts, compare network activity with your personal engagement heatmap.
• For experiments, write down the network context so you do not overread one result.

Your own followers matter more than the whole network. But the whole network explains some of the background noise.

How to use follow events

Follow events show account-connection activity. When follows are high, people are discovering accounts, joining communities, or reacting to an event.

For growth work, this helps when you are publishing a thread, joining a Starter Pack, or participating in a live conversation. A high-follow period may be a good time to be visible.

A network-wide follow spike only says people are making connections on the network. Your account still needs a reason to be followed.

How to use posts by hour

Posts by hour is the most practical chart on the page.

It shows the shape of recent activity in your local timezone. That helps when generic "best time to post" advice feels too broad.

For example:

• If posts are climbing, the network is waking up or reacting to something.
• If posts are flat, activity is steady enough for normal scheduling.
• If posts drop sharply, wait before judging a post's first-hour engagement.

Pair this with your own Bluesky Analytics. Network activity tells you when Bluesky is busy. Your analytics tells you when your followers respond.

How to use top languages

Top languages show the language tags found in recent public posts.

This is useful when your audience is multilingual or when a conversation feels bigger than your feed. A spike in a language you do not usually watch can explain why the network feels active while your normal community feels quiet.

Use it for context:

• check whether a trend is happening outside your usual language community
• decide whether to localize a post
• avoid assuming English-language feeds represent the whole network

Language labels are a directional signal. Users and apps can omit or mislabel language metadata.

How to use top linked domains

Top linked domains show which domains appear most often in recent public posts with links.

For social listening, repeated domains can point to a story people are sharing or arguing about. Inspect the conversation before posting into it.

I would use top domains for:

• spotting fast-moving news links
• deciding whether a link post fits the current mood
• finding sources that people are already discussing
• checking whether your own domain appears during a campaign

The domain list does not tell you sentiment. A domain can be trending because people like it, criticize it, or argue about it.

What these stats do not tell you

Network stats are easy to overread.

These stats do not tell you:

• how many people saw your post
• whether your followers were online
• whether a topic is positive or negative
• whether one community is more important than another
• whether a post will perform well

They are a context layer.

Use Bluesky Analytics for post performance. For posting time decisions, start with your personal heatmap and then check the network activity page. Trend work still needs the actual posts; use stats to decide where to look.

A simple workflow

Before an important Bluesky post, I would check three things:

• Your personal analytics: when your followers usually engage.
• Bluesky Stats: whether the public network is unusually active or quiet.
• Search/custom feeds: what people in your topic are actually saying.

Then schedule the post with TheBlue.social or post manually if it needs to join a live conversation.

That gives you enough context for normal posting. No need to turn every post into a research project.

Last updated: June 15, 2026