Telegram RegisterThe public register of Telegram
Telegram profile photo for Roxy-WI

Channel

Roxy-WI

@roxy_wi_channel

On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Cite this entry

226subscribers

+4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001458917949
TypeChannel
Username@roxy_wi_channel
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live4 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/roxy_wi_channel

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

2222262247 August 2026 — 222 subscribers8 August 2026 — 222 subscribers31 August 2026 — 224 subscribers10 September 2026 — 223 subscribers19 September 2026 — 224 subscribers4 October 2026 — 226 subscribers7 August 20264 October 2026
6 measurements spanning 58 days, net +4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 221–227 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 12:41226+2
19 Sept 2026, 05:39224+1
10 Sept 2026, 08:19223-1
31 Aug 2026, 09:14224+2
8 Aug 2026, 10:32222no change
7 Aug 2026, 23:18222first reading

Engagement

18 posts held, back to 27 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

16 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 43.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥743.8%
👍637.5%
🥰318.8%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 7 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 27 August 2025 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 14:56 UTC35 viewsread 8 August 2026
Poll

One more good news about Roxy-WI! We have refactored its terraform provide. Fix bugs, enchantes its flow. Have you tired Roxy-WI terraform provider?

  1. Yes60%
  2. No40%
  3. Wow! There is provider!0%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

3 Aug 2026, 15:34 UTC109 views2 reactionsread 8 August 2026
Photo

It's been a while since we've seen an interesting update to Roxy-WI, and we need to fix that. The new version will feature a dependency map for Nginx, in an updated and convenient format. The map for HAProxy has also been updated.

🔥2

22 Jul 2026, 14:34 UTC194 views4 reactionsread 8 August 2026

The IncidentRelay Blog is live! We’re writing about the practical side of on-call and incident response — without the corporate fog machine. The first guides cover: • Designing on-call schedules that survive weekends and vacations • Building fair rotations for small SRE teams • Creating escalation policies that don’t page the entire company • Reducing alert fatigue with measurable improvements • Running a self-host…

👍4

13 Jul 2026, 06:28 UTC220 viewsread 8 August 2026
Photo

Good news everyone! Two releases today! First stable realse of IncidentRelay and Terraform provider for it. BTW, on the pic IncidentRelay heartbeat feature ;)

22 Jun 2026, 14:20 UTC339 viewsread 8 August 2026

Unfortunately, new installations may encounter issues due to OpenSSL updates. Read this to stay informed.

2 Jun 2026, 06:01 UTC370 views3 reactionsread 8 August 2026

RMON was released today, and now RMON can send alerts to IncidentRelay. Let's create our own ecosystem! 😁

🔥3

16 May 2026, 05:16 UTC367 viewsread 8 August 2026

BTW, we have created a small site for IncidentRelay. Reading docs more comfortable, than on GitHub

15 May 2026, 06:26 UTC279 viewsread 8 August 2026

Today is a day of Roxy-WI updating! Do not forget update it to the latest version. There are a lot of security fixes.

4 May 2026, 07:36 UTC373 views2 reactionsread 8 August 2026
Photo

A bit screenshots from IncedentRelay

👍2

4 May 2026, 06:29 UTC268 views2 reactionsread 8 August 2026

🚨 Introducing IncidentRelay — a self-hosted on-call and alert routing service IncidentRelay helps teams receive, route, acknowledge, and resolve alerts without relying on a hosted incident-management platform. What it can do: • Route alerts from Alertmanager, Zabbix, and generic webhooks • Manage teams, groups, users, and on-call rotations • Send notifications to Mattermost, Slack, Telegram, Discord, Microsoft Tea…

🔥2

1 May 2026, 12:39 UTC211 viewsread 8 August 2026
Poll

Do you use any on-call system like Grafana on-call, pagerduty or incedent.io?

  1. Yes67%
  2. No22%
  3. I've never heard about these systems33%

The shares total 122%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

21 Dec 2025, 04:53 UTC≈1,060 viewsread 8 August 2026

Unfortunately, a bug was discovered in version 8.2.6. Version 8.2.6.1 has been released to fix it. Please update Roxy-WI and restart the roxy-wi-metrics service after the update.

Showing the 12 most recent of 18 posts we hold for @roxy_wi_channel. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Polls

The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

7 Aug 2026, 14:56 UTCAnonymous Poll5 voters

One more good news about Roxy-WI! We have refactored its terraform provide. Fix bugs, enchantes its flow. Have you tired Roxy-WI terraform provider?

  1. Yes60%
  2. No40%
  3. Wow! There is provider!0%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

1 May 2026, 12:39 UTCAnonymous Poll9 voters

Do you use any on-call system like Grafana on-call, pagerduty or incedent.io?

  1. Yes67%
  2. No22%
  3. I've never heard about these systems33%

The shares total 122%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

27 Oct 2025, 08:16 UTCAnonymous Poll16 voters

Have you already tried config wizard for Nginx?

  1. Yes, and it's great!38%
  2. Yes, but nothing special13%
  3. Yes, it's uncomfortable6%
  4. No, I still edit it directly0%
  5. No, I don't use Nginx with Roxy-WI13%
  6. No, I don't use Nginx at all31%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 18 most recent posts we hold, published 27 August 2025 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 4 October 2026 — this entry's latest reading, not the date you are reading this.

“Roxy-WI” (@roxy_wi_channel), 226 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/roxy_wi_channel.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.