Back to @githubstatus's profile

GitHub Status engagement report

@githubstatus - 119K followers on X

Measured over 40 original posts from a 30-day window, last computed on October 6, 2026.

Engagement

Bottom quarter for its size
Per follower
0.005%
of 119K followers
Per impression
0.173%
3.5K views on a typical post
Reach
2.92%
of its followers see a post
Typical post
6
interactions (median)
Saved
0%
0 bookmarks on a typical post
Posting rate
1.33/day
active 23% of days
Peak time
21:00 UTC
Monday

A typical post picks up 6 interactions against 119K followers, an engagement rate of 0.005%. Measured over 40 original posts, its engagement rate beats 12% of 15,519 tracked accounts of a similar size. That is a reason to look at how the audience behaves - reply depth, saves, whether the followers are recent - rather than a conclusion about it on its own. Posts are seen about 3.5K times each, and 0.173% of those impressions turn into an interaction. That is about 2.92% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.3 post a day over the last 30 days, though only 23% of days saw any activity at all. Most posts go out around 21:00 UTC, and Monday is the busiest day of the week. Of the 40 posts sampled, 100% link out. The account's strongest tracked post pulled 43 interactions, about 7.2x its own typical post.

Measured over 40 original posts from a 30-day window, last computed on October 6, 2026.

Compared with accounts its own size

GitHub Status's engagement rate beats 12% of the tracked X accounts closest to it in follower count (15,519 accounts, accounts of similar size (decile 7 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.

On engagement per impression rather than per follower it beats 9% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.

Where this sits in the catalog

At 0.005%, GitHub Status sits above the 10th percentile of the 157,102 accounts in this comparison. That places it in the bottom 25% band, which runs below 0.022%.

p100.003%
p250.022%
p50 (median)0.128%
p750.604%
p902.32%
p9983.4%
Engagement rate as a share of followers, across the 157,102 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 26,052 times apart and a linear axis would flatten everything below the median into a single point.
Show the percentile table
Engagement rate percentiles
PercentileEngagement rate
10th percentile0.003%
25th percentile0.022%
50th percentile0.128%
75th percentile0.604%
90th percentile2.32%
99th percentile83.4%

This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built

Posting timing

This account posts most often around 21:00 UTC, and Monday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.

Engagement by hour posted, UTCTwenty-four bars, one per UTC hour. Each bar shows how posts published in that hour compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest hour: 21:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 21:00 UTC
Show engagement by hour posted, utc as a table
Engagement by hour posted, UTC
Hour (UTC)Vs author medianPosts
00:00 UTC-1%89K
01:00 UTC-2%90K
02:00 UTC-3%88K
03:00 UTC-4%94K
04:00 UTC-5%76K
05:00 UTC-4%75K
06:00 UTC-5%86K
07:00 UTC-5%93K
08:00 UTC-4%108K
09:00 UTC-4%124K
10:00 UTC-3%129K
11:00 UTC-3%141K
12:00 UTC-3%154K
13:00 UTC-3%167K
14:00 UTC-4%173K
15:00 UTC-2%176K
16:00 UTC-3%171K
17:00 UTC-3%159K
18:00 UTC-2%149K
19:00 UTC-2%141K
20:00 UTC-1%131K
21:00 UTC0%116K
22:00 UTC-2%100K
23:00 UTC-1%90K
Engagement by day of weekSeven bars, one per weekday, Sunday first. Each bar shows how posts published on that day compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest day: Monday.
SunMonTueWedThuFriSat
Above the authors' own mediansBelowScale: plus or minus 111%Busiest day: Monday
Show engagement by day of week as a table
Engagement by day of week
DayVs author medianPosts
Sunday+5%393K
Monday+1%483K
Tuesday-2%520K
Wednesday-3%472K
Thursday-2%430K
Friday-3%447K
Saturday+2%393K
See what moves engagement across the whole catalogWhat counts as a good engagement rate at this size

Formats this account uses

Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.

This account's posting mix compared with catalog-wide effects
FormatThis accountCatalog effect95% intervalAccounts behind it
Image or video0% of posts+111%+108% to +115%34K
Outbound link100% of posts-41%-42% to -40%32K
Typical length--3%-3% to -2%54K
  • 0% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
  • 100% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts, so a large share of this account's output sits in the weakest bucket we measure.
  • Its average post runs 178 characters, which falls in the 80 - 180 characters band. Across the catalog, posts of 80 to 180 characters run 3% below the same accounts' other posts.

These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.

Best tweets

  • Oct 5, 20267.2x their median

    We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more. https://t.co/FTKQ5TH9NN

    235784.9K viewsView on X
  • Oct 5, 20265.0x their median

    We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more. https://t.co/FTKQ5TH9NN

    182914.3K viewsView on X
  • Oct 5, 20264.0x their median

    Actions is operating normally. https://t.co/FTKQ5TH9NN

    193202.6K viewsView on X
  • Oct 5, 20263.8x their median

    Actions is experiencing degraded availability. We are continuing to investigate. https://t.co/FTKQ5TH9NN

    95634.1K viewsView on X
  • Oct 5, 20263.0x their median

    We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we le... https://t.co/FTKQ5TH9NN

    121323.2K viewsView on X
  • Sep 28, 20263.0x their median

    Copilot Code review has recovered, for reviews that were previously not successful you can re-request review from your PR. https://t.co/YDYIXWI101

    132304.3K viewsView on X
  • Oct 5, 20262.7x their median

    We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting... https://t.co/FTKQ5TH9NN

    124002.6K viewsView on X
  • Oct 5, 20262.3x their median

    We are investigating reports of degraded performance for Actions https://t.co/FTKQ5TH9NN

    90323.5K viewsView on X
  • Oct 5, 20262.0x their median

    In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation. https://t.co/FTKQ5TH9NN

    83102.7K viewsView on X
  • Oct 1, 20262.0x their median

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. https://t.co/NZL5pAcqQk

    82205.5K viewsView on X

Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.

Buy or sell Twitter (X) accounts - escrow-protected

PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.

Reading these numbers

A typical post picks up 6 interactions against 119K followers, an engagement rate of 0.005%. Measured over 40 original posts, its engagement rate beats 12% of 15,519 tracked accounts of a similar size. That is a reason to look at how the audience behaves - reply depth, saves, whether the followers are recent - rather than a conclusion about it on its own. Posts are seen about 3.5K times each, and 0.173% of those impressions turn into an interaction. That is about 2.92% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.3 post a day over the last 30 days, though only 23% of days saw any activity at all. Most posts go out around 21:00 UTC, and Monday is the busiest day of the week. Of the 40 posts sampled, 100% link out. The account's strongest tracked post pulled 43 interactions, about 7.2x its own typical post.

What is GitHub Status's engagement rate on X?
GitHub Status (@githubstatus) has an engagement rate of 0.005%, based on the median interactions across 40 original posts from the last 30 days against 119,021 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.005%, GitHub Status sits above the 10th percentile of the 157,102 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
Does @githubstatus have real engagement?
Its engagement rate beats 12% of the tracked X accounts closest to it in follower count (15,519 accounts), which puts it in the bottom quarter for its size group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
When does @githubstatus post?
Most posts go out around 21:00 UTC, and Monday is its busiest day, at roughly 1.33 posts per day across the measured window.

Keep going